Maria Fernanda Godoy Fuenzalida

Hi team!

I'm sharing the following idea with you:

Exporting and Importing database between UAT environments takes time and human interaction that could be avoided. This could be better and faster if the process automates with some parameters such as Source database, Destination database, time of operation to avoid downtime, etc.

If the process in this article could be automatic and programmed, it would save a lot of time for customers

Import a database - Finance & Operations | Dynamics 365 | Microsoft Learn

Best regards.

Users from a French company ask us to change the “FR” translation of the standard labels because according to them the standard French translation is incorrect. Below is the list of labels for which users have requested a new translation:

Label ID: @SYS116959

Label translation en-us: Carrier Company

Label translation fr: Société de transport

Suggested Label translation fr: Transporteur

Label ID: @SYS11959

Label translation en-us: Unit

Label translation fr: Unité

Suggested Label translation fr: Unité de gestion

Label ID: @SYS12836

Label translation en-us: Item number

Label translation fr: Numéro d'article

Suggested Label translation fr: Code article

Label ID: @SYS190813

Label translation en-us: Unit

Label translation fr: Unité

Suggested Label translation fr: Unité de gestion

Label ID: @SYS23010

Label translation en-us: Customer reference

Label translation fr: Référence client

Suggested Label translation fr: Info de client

Label ID: @SYS334404

Label translation en-us: Units

Label translation fr: Unités

Suggested Label translation fr: Nb de colis

Label ID: @SYS50389

Label translation en-us: Shipment

Label translation fr: Expédition

Suggested Label translation fr: N° d’expédition

Label ID: @SYS50253

Label translation en-us: Pallet ID

Label translation fr: ID palette

Suggested Label translation fr: N° PALETTE

Label ID: @SYS8928

Label translation en-us: Open quantity

Label translation fr: Quantité en cours

Suggested Label translation fr: Quantité commandée

Label ID: @SYS9694

Label translation en-us: Sales Order

Label translation fr: Commande client

Suggested Label translation fr: N° de commande

Label ID: @WAX258

Label translation en-us: Load ID

Label translation fr: Référence de chargement

Suggested Label translation fr: N° de chargement

Label ID: @WAX273

Label translation en-us: Work ID

Label translation fr: Référence de production

Suggested Label translation fr: Ordre de préparation

Label ID: @SYS12529

Label translation en-us: Confirmation

Label translation fr: Confirmation

Suggested Label translation fr: N° version

Label ID: @WAX275

Label translation en-us: Shipment ID

Label translation fr: Référence d'expédition

Suggested Label translation fr: N° d’expédition

Label ID: @SYS23422

Label translation en-us: Customer requisition

Label translation fr: Demande d'achat client

Suggested Label translation fr: N° d’achat client

Label ID: @SYS316092

Label translation en-us: Incoterms

Label translation fr: Incoterms

Suggested Label translation fr: Incoterm

Label ID: @SYS828

Label translation en-us: Payment

Label translation fr: Paiement

Suggested Label translation fr: Conditions de règlement

Label ID: @SYS103211

Label translation en-us: Site

Label translation fr: Site

Suggested Label translation fr: Site d’expédition

Label ID: @SYS10500

Label translation en-us: Line amount

Label translation fr: Montant de ligne

Suggested Label translation fr: Montant de ligne H.T. 

Label ID: @SYS23780

Label translation en-us: Customer code

Label translation fr: NUMÉRO CLIENT

Suggested Label translation fr: Client facturé

This would benefit the French end users, and will avoid misunderstandings in the concepts.

At this time CustVendItemGroup exists as a table. Unfortunately, it does not exist as an entity.

CustVendItemGroup as an entity can bring more usages for the table itself and for future integrations in other products.

Workflow history can show different aspects of the workflows. The problem comes when filtering for users that are not assigned for that workflow or any workflow. So, we have the following situation:

· User A has a workflow assigned

· User B does not have any workflow assigned

· User B can see the workflows escalated or delegated to User A (and any other user in any other company)

In terms of restricting the information available, this is not working as expected. Everybody can view purchase orders, invoices and travel expenses that should not be viewed. The user should view only those records where the user itself is involved.