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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer Service forum / Data Export - Global O...
Customer Service forum

Data Export - Global Option Set not synchronising

(0) ShareShare
ReportReport
Posted on by Community Member

We have noticed that a global option set has not been synchronised between CRM and the Azure SQL server. When the Export config is inspected, the "Last sync status" of the meta-data is "Partial Failure".

I've tried to inspect the logs through the Failed Records tool, but it only contains error messages for entities of the solution, not meta data such as global option sets.

Does anyone have a suggestion as to how I can see what's gone wrong?

Categories:
Customer Service
I have the same question (0)
  • Fabrice Kwetchet Profile Picture
    Fabrice Kwetchet 5 on at

    Hi there, we are facing the same issue :(

    Any updates on this issue

  • Community Member Profile Picture
    Community Member on at

    We also appear to be having the same problema, and it appears to be mixing up Global Option Sets with Entity specific option sets. Anyone found a solution or what might be going on?

    Regards

  • Community Member Profile Picture
    Community Member on at

    Hi,

    The update to this is slightly meandering.

    The original issue of "partial failure" was noticed because our global option sets did not appear to be present in the exported GlobalOptionSetMetaData table.

    Investigating the synchronisation status, we noticed that there was a partial failure - hence the original question of how to address this issue.

    I don't have any more information about how to resolve the partial failure of the synchronisation except re-doing the export profile and database. This is likely overkill however, and not guaranteed to resolve the issue.

    In case anyone else suffered from the same problem of Global Option sets not appearing, I have found that Global option sets appear under the name they are instantiated on an entity. If you use a global option set on three entities, the GlobalOptionSetMetaData table will contain that option set three times, under the three names it appears against on those entities. When we looked for our "missing" global option sets under their instantiated names, we were able to find them all, even with the partial failure.

    Hope this helps

  • Community Member Profile Picture
    Community Member on at

    Thanks for the info ConnorK.

    In our case we haven't got any partial failures, and we can't find some  of the options sets description values, most are there but not all. 

    It's an option set used in Appointment entity, with an option set name of typeappointment. In Setting, customization etc in the entity we can clearly see the option set and descriptions, yet we cannot find the set anywhere in the data export table. Other option set from the same entity are included, which is really baffling us!

    Will continue to explore but can't see that there's much to do other than recreate the profile etc, as you say seems a bit much. 

  • Tim Burgoine Profile Picture
    Tim Burgoine 15 on at

    I know this is an old thread, but thought I would log this here in case anyone else still has this issue.

    When the Global OptionSets are being replicated they are using the fields name and not the Optionset id.  this means that if you are using the same field name on different tables then you will lose one of the optionsets from the sync data.  I have 2 fields both have an id of "xx_source" but they use different Global OptionSets ("xx_ParkSource" and "xx_SiteSource").  but only 1 of the optionset made it into the replication, and they have set the OptionSetName as "xx_Source", which won't be unique!  we have been running the system for too long to resolve this by replacing the fields.  (Note for next project - MAKE SURE set your fieldname to be the same as your global optionset name, so that the replication works)

    I am waiting for MS to confirm that this is the case and what is going to be the resolution.  

  • Prathmesh Profile Picture
    Prathmesh 15 on at

    Hi Tim,

    We are facing same issue with the DES replication where only one OptionSet gets replicated. Any response you received from MS about this issue? Can you please share the response/update from MS?

    It would be really helpful for the community folks landing on this page with this issue.

    Thanks!

  • Tim Burgoine Profile Picture
    Tim Burgoine 15 on at

    Sorry, I had forgotten that I had posted this.  

    The result from Microsoft was a patch that added the Global Optionset identifier to the output, so the optionset are no longer blocked.  You will have to ask MS for the Patch, they will give you a SQL script that you run against your DB, and they need to update the data export settings in the background.

    Once this patch is installed it should work perfectly from there.

  • Prathmesh Profile Picture
    Prathmesh 15 on at

    Thanks Tim. We reached out to Microsoft as well and got same response.

    Basically they gave us two SQL scripts to run on our DB and they turned on some feature flag in the background.

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Customer Service

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans