web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / What to check when BYO...
Finance | Project Operations, Human Resources, ...
Answered

What to check when BYOD export - executing very long

(0) ShareShare
ReportReport
Posted on by ShaqAX 709

Hi guys,

When export to BYOD, under same Export Job I have 4 tables (entities), while the 1 table succeeded, the other 2 is still executing like it is stuck.

I ran to similar topic as this is, and mentioned it is resolved by Update version to 10.0.21, however mine already updated as below :

- Installed product version : 10.0.21 (10.0.960.43)
- Installed platform version : Update45 (7.0.6129.38)

This is the topic which is similar to me -> community.dynamics.com/.../1192018

Another info is, this is still in Tier-1 export to Azure SQL DB and the data also very small ( < 100 records). I also skip staging table for all 4 entities.

Any clue why and how to resolve this ? 

Out of 4, 1 of it also Partially succeeded, but if I check the Execution Log, only mentioned how many records exported which is the correct number I expected. Same thing if I check Infolog.

I would also like to know why the status is Partially succeeded when all records is exported correctly.

Please help.

Thanks,

I have the same question (0)
  • Suggested answer
    A.Prasanna Profile Picture
    A.Prasanna 8,223 on at
    RE: What to check when BYOD export - executing very long

    Hi

    which entities have you are published?

    most of the time it will depend on the volume of your transactions and the Performance Tier of your Azure SQL (BYODB). Check your BYODB utilization from Azure Portal, have you tried with Incremental push, or are you trying with Full push? ,

    Regards,

    AP

  • ShaqAX Profile Picture
    ShaqAX 709 on at
    RE: What to check when BYOD export - executing very long

    Hi Amith,

    It is my custom entities, related to ProjInvoice (Item/Empl/Cost). May I know how to check the BYOD utilization in Azure Portal ?

    From the start actually I'm choose Incremental push, will that ok ? or every time we should Full push first then Incremental ?

    Thanks

  • Suggested answer
    A.Prasanna Profile Picture
    A.Prasanna 8,223 on at
    RE: What to check when BYOD export - executing very long

    From my experience, for Master data, you can use (scheduled) full push, but if you have transactional data, the best option is incremental, but anyway you will need to do one full push for the first time.

    to get better visibility of the performance you can use Azure SQL Analytics but it is still under preview but I think worth trying it. Refer to the below link.

    docs.microsoft.com/.../azure-sql

  • Suggested answer
    Alireza Eshaghzadeh Profile Picture
    Alireza Eshaghzadeh 14,637 Super User 2025 Season 2 on at
    RE: What to check when BYOD export - executing very long

    Hi ShaqAX,

    Can you export data for these entities full push to AzureSQLDB?

    Have you already checked provided feedback on the community.dynamics.com/.../1192018?

  • Suggested answer
    Cristina Perez Profile Picture
    Cristina Perez on at
    RE: What to check when BYOD export - executing very long

    Hi!

    In addition to Amith Prasanna and Alireza Eshaghzadeh comments, please kindly check the following:

    The performance in export to BYOD scenarios is handled by FinOps but also by your Azure SQL BYOD. If you BYOD is busy (please see the load in your BYOD from Azure Portal) this will definitively impact in a negative way the performance of the export.

    Additionally you can check the following best practices:

    1) Export using batch instead of synchronous exports. Try creating a separate batch group with N-1 AOS' and use this batch group to process the exports during off business hours.

    2) Use only fields which are required and remove unnecessary fields from mapping

    3) Try using Skip staging option wherever possible

    4) Use incremental exports and limit the number of columns which needs to tracked using only primary table change tracking or custom query

    5) Use full push for data entities where we have large number of joined data sources creating complex change tracking union queries --- As example General journal Entities -- don't enable change tracking for all datasources.

    6) Clean- up staging tables regularly using the new feature of job history clean-up

    7) Review the Tier of your BYOD Database and the load

    If you still have some problem, you can anytime raise a support request with us.

    Hope this helps!

    Have a good day

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 813

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 738 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 566 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans