0
Category:
STATUS DETAILS

Comments

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.

Category:

This would be incredibly useful since many users will only use a very limited amount of the functinality available, and personalization is key to make the user experience easy and understandable.

Category:

Great suggestion. Would like to see more upvotes. This is on our backlog and will just need to be prioritized.

Category:

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.

Category:

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.


Category:

Hi Shahhista,

This is available today. You can simply enter a custom 'Type' to describe any data field.

One advantage of using custom types is that fields from different source tables with the same custom type will automatically be configured to be merged in the final step of unification.

Category:

I noticed this one has been under review for a few months, is this still in consideration?

Category:

This requirement is consistently asked by various clients in recent months so it would be great if this can be implemented.

Category:

This is really essential for Canadian users. EFT payments in US funds from a CAD company is very common. It should be possible to generate both Vendor Remittance and EFT files in the currency of the bank account used. The functionality should work with Data Exchange Definitions that use either the "ACH" or "ACH RB" table sets.

Category:

A link to download is NOT AN ATTACHMENT. The need is specifically for SENDING ATTACHMENTS. We run into this from customers all the time. Compliance is concerned with links that download files. Most competitive products have this feature.

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 500