wp-user-frontend domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/theomnibuzz/public_html/wp-includes/functions.php on line 6114wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home2/theomnibuzz/public_html/wp-includes/functions.php on line 6114Integrations are something that we’re familiar with – whether it’s a custom integration tailored for one of our customers or it’s utilizing our popular pre-built solution CRM For Distribution. Microsoft added alternate essential support to Integrations , allowing us to improve integration speed significantly.<\/span><\/p>\n
One challenge that we’ve had in the past was speed. In other words, how much time it takes to get your data from another system into Perfex 365 Customer Insights<\/a>? If all that’s needed is to Create records, then speed usually isn’t an issue. The challenge comes into play when data already exists in Integrations , or you need to backfill data. This could sometimes take several days to several weeks! One of the main reasons for this was that this required two steps:<\/span><\/p>\n
That might not seem like much, but if you can imagine trying to backfill thousands or millions of rows of data, this can take a considerable toll on performance.<\/span><\/p>\n
A few years ago, Microsoft began allowing perfex crm setup<\/a> developers to use Upsert statements. Upserts can dramatically improve the speed of your data processing. Instead of making two separate calls to Dynamics 365, an Upsert allows for one ring to determine if a record needs to be updated or Created based on a unique key. The Key defines the unique identifier for the record (using one field or a combo of areas).<\/span><\/p>\n
You may run into a challenge when creating Alternate Keys in an existing Dynamics 365 organization if it already contains duplicate records as defined by the Key. In that case, you will notice that the Key status is set to Inactive. To Activate it, you must eliminate the duplicate records, either by deleting the duplicates or removing the values on one of the corresponding fields for each same record.<\/span><\/p>\n
You can find duplicates in Integrations in a couple different ways:<\/span><\/p>\n
Create and publish a duplicate detection rule. Then, run an exact detection job on all records for that entity. This process works well for the most part but can be slow if you have a ton of data.<\/span><\/p>\n
\u00a0<\/span><\/strong>Use the Dynamics 365 SDK or 3rd party tools to help you identify duplicates within minutes.<\/span><\/p>\n
While Dynamics 365 allows you to merge records, this does not remove the duplicate record from the database so that the alternate Key will remain Inactive. You can give your end users control over which duplicate records are released by instructing them to merge the documents or utilising a custom merge process. Then, use an automated process to delete the Inactive merged records.<\/span><\/p>\n
We’ve been implementing alternate keys with Upserts in our data integration solutions for our customers, and we have seen an incredible improvement in speed! It allows us to push more data promptly, and the keys help enforce record uniqueness at the database level, making our customers happy.<\/span><\/p>\n
If you want to learn more about how you can improve Dynamics 365 data integrations with alternate keys, contact Beringer today!<\/span><\/p>\n
0<\/p>\n
0<\/p>\n
0<\/p>\n","protected":false},"excerpt":{"rendered":"
Integrations <\/p>\n","protected":false},"author":61177,"featured_media":981994,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_kadence_starter_templates_imported_post":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[131],"tags":[],"yst_prominent_words":[],"class_list":["post-981997","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business"],"_links":{"self":[{"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/posts\/981997","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/users\/61177"}],"replies":[{"embeddable":true,"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/comments?post=981997"}],"version-history":[{"count":0,"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/posts\/981997\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/media\/981994"}],"wp:attachment":[{"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/media?parent=981997"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/categories?post=981997"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/tags?post=981997"},{"taxonomy":"yst_prominent_words","embeddable":true,"href":"https:\/\/theomnibuzz.com\/wp-json\/wp\/v2\/yst_prominent_words?post=981997"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}