You can usually detect a bad date returned by one of the queries below when ran against the Dynamics SL application databases: select distinct fiscyr from gltran order by fiscyr select distinct fiscyr from accthist order by fiscyr select distinct fiscyr from curyacct order by fiscyr select distinct perpost from gltran order by perpost Note that a valid year would be between: Minimum year allowed: 1000 Maximum year allowed: 9999 Also note that a blank record from the queries above would not be a valid year. You will need to work with the Dynamics SL team to identify a data issue. Once the data issue is resolve reconfigure the data mart integration using the following steps. Reconfigure the Dynamics Data Mart integration. 1. Start the MR Configuration Console. 2. Under ERP Integrations, select the Dynamic Data Mart integration. 3. Click Remove to remove the integration. 4. In SQL Management Studio, delete the DDM database. 5. In the MR Configuration Console, click File and then click Configure. 6. Select Add Microsoft Dynamics Data Mart and then click Next. * Select Enable on the Initial Integration The error message "Reader returned fewer objects for processing" is a more of a warning and can be ignored if it doesn't continue to occur consecutively.
↧