Comments
This would be great, additionally the set could be versioned.We use many options sets to refer to government rules that change over time. Rule 1 might mean something during the years 1997-2011, and then might have another meaning through 2011-present. option versioning and deactivation would be perfect!
We are implementing GTIN13 codes at a customer. The GTIN codes are printed on the labels and are used by the end-customer in their shops for product identification for instance at POS. On the label, the 13 digit code is printed. All whs scanning flows are using the 13 digit GTIN code. Since D365FO puts a leading zero to the GTIN13 code, we cannot use the code for scanning, since the 13 digit code is not recognized. Adding a leading zero to the barcode is no option, since this will make the barcode unusable during the supply chain (distributors, wholesalers, stores).Why is this leading zero added to the GTIN code? This is really annoying for interfaces as well, where we have to take the leading zero's away.
We are adding this suggestion in the coming months.When adding a new table to Customer Insights, you will be able to easily select what columns to include or exclude.This release plan speaks to this capability in the context of the Dataverse connector, but the capability will be for any table ingested into Customer Insights - Data.
Hi Testlog,By 'remove unification' I assume are trying to remove one or more tables from the unification configuration.This is definitely a pain point, and we're looking at providing an option to remove a table and all downstream dependencies, such as rules, segments.If you're looking to accomplish some other task, let me know.