We’re currently on version 10.0.11 and using BYOD to export General Journal Account Entry Entity (daily 60k records).Ā Incremental push no longer works, we’ve had to move to full push which also regularly fails but gets fixed by dropping entity.Ā Has anyone else had issues with this entity? One of the proposed solutions (apart from moving to 10.0.12) was to use a new entity General Journal Account Entry Reporting however testing on this has also been unsuccessful.
Regards
Eric #Financeandoperations #BYOD
??
—————————— Eric McMahon Brisbane ——————————
Joe MacPherson
Member
August 28, 2020 at 7:17 AM
Hello Eric;
You’re not alone on the BYODB Incremental Export woes…Ā We experienced these challenges early on in our D365 journey starting with v7+, through v8+ and onto v10+… Our record volumes were just too high to execute a full nightly export across multiple Entities; our solution was to build our own Incremental process through the following steps: (high level overview)Ā
Creation of an ‘Azure’ (BYODB) Production database
Onetime Full Entity export to populate the Production database Entity tables
Creation of an ‘Azure’ (BYODB) Staging database
Nightly Data Management Export projects with Entity specific filtering on targeted key fields (Created/Modified date)Ā
Entities have to be reviewed for key target filtering fields
Custom Stored Procedures to “Merge Into [AX_PRODUCTION].[dbo].[GeneralJournalAccountEntryStaging] as Target”
SQLAgent execution jobs to validate that the ‘filtered’ Entity was in a READY state and then Execute the MERGE Stored procedure
Be more than glad to talk this through off line if you desire. Joe
—————————— Joe MacPherson Coldwater Creek Hingham MA —————————— ——————————————-
Sarah Poe
Member
August 28, 2020 at 3:10 PM
Hi Eric,
We also had an issue with this entity, and many others.Ā We ended up having to create custom entities.Ā If you need more information, please feel free to reach out directly.
BYOD has been a big struggle for us, so we feel your pain!
—————————— Sarah Poe Luck Stone Corporation Richmond VA —————————— ——————————————-
Eric McMahon
Member
August 29, 2020 at 1:57 AM
Thank you Sarah & Joe. Despite strong advice not to go the custom entity route we may need to do that as well as some filtering.Ā I’ll let you know how we go.
Glad to report our issue was resolved and now runs in less than a minute (60k rows per day incremental load). The MS backend team discovered that the query planĀ on the table was was sub optimal and updated statistics to force a better query plan. On going a full scan is set with Persist_sample_percent set to on. It’s been running successfully for a number of weeks now. ??
—————————— Eric McMahon Senior Advisor Queensland Treasury Corporation —————————— ——————————————-
Please note:
This action will also remove this member from your connections and send a report to the site admin.
Please allow a few minutes for this process to complete.
Report
You have already reported this .
Welcome to our new site!
Here you will find a wealth of information created for peopleĀ that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!