Sunil Garg PRINCIPAL GROUP PROGRAM MANAGE

Please support/implement the „upsert“ functionality for the OData service endpoint. (According http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html “11.4.4 Upsert an Entity”)

Without this feature, an OData client has to perform a GET request first, to check if the record already exists or not. Than perform a POST or PATCH/PUT. Currently, unnecessarily many requests are needed.

When using Data entities of Vendor invoice header and Vendor invoice lines , it does not contains the fixed asset record in the PO Line, this causes an issue when importing invoices which should have fixed asset assigned in the PO Line. The actual result now the asset record disappeared. This need to be addressed to ensure Data entities of Vendor invoice header and Vendor invoice covering this scenario. 

Since the PU10 upgrade, whenever I try to import a user with a Person that is already assigned to another user using the "User information" data entity, I receive the following error:

https://imgur.com/a/Lfx9q

When you try to create a user manually from the UI (System administration >> Users >> Users), the person name is being picked up from a lookup table containing many fields, in particular 'Employee name' and 'Party ID'. The 'Party ID' is the primary key, i.e. it can distinguish between two persons having the same name. However, the "User information" data entity does not contain this field and whenever I try to import two or more users under the same person, I receive the error specified in the link above.

What I suggest as a resolution is that the 'Party ID' is included in the data entity so that it would be much easier to distinguish one party from another.

When setting up and creating files which can be used to populate a company with data, it would be helpful if we could somehow make the Data Management Framework support a sub string replace mechanism. For example, we could mark certain columns/fields on Data Entities to tell the Framework a column/field should check for sub string replacements. The Framework could then run the value of the field against a sub string replace method that looked for certain predetermined fixed strings and replace them with the correct runtime value.

Example, if we needed to reuse the same data package across multiple companies, but we wanted to have the Company ID replaced in the data, we could put in #CompanyID# in the csv/spreadsheet, and the Data Management Framework would do the work. This assumes the column was selected for such an operation. 

Other suggested replacement terms could be CompanyLanguage and CompanyCurrency. A typical use of CompanyID as sub replacement string is when injecting number sequences and you want the company ID as part of the number sequence name, not to mention any other entities referring number sequence names. 

Data Mangement Framework support full value replacement today, but this idea is to support a sub string replacement function against a predetermined fixed set of "macro words". In theory it could be extended to support additional magic words by a ISV/VAR if necessary.

If a Company wants different matching policy for ex. internal vs external vendors and/or sales items you now have to go in to each seperate LE and change Matching Policy. It would be faster to copy the settings between legal entities using Data Management (if this was an available entity). Can you create an entity for this in the nearby future?

Thank you.

There needs to be a way for developers to handle cross company table relations within a data entity. There are two scenarios that developers should be able to handle:

1. A join between tables with no consideration of dataareaid
   1. For example, we have a RecId reference in a table and want to join on just that recid.
2. A join between tables using a dataarea reference
   1. For example, using the ProjectDataAreaId field in TSTimeSheetLine table to join to the ProjTable
      1. Currently we can define this relation, but when the database is synced it includes TSTimeSheetLine.DataAreaId = ProjTable.DataAreaId.

This feature should also support change tracking.

While exporting data through Data Management there is a size limit that currently set to 256MB. Following link refers to it: https://fix.lcs.dynamics.com/Issue/NotFixed/?bugId=3824019&qc=103b9b18eb6754aaa53dd906fa35037b9a803b5c398a816910becb3f1ae9aa81

However, with the increasing data volume over the time in your ERP this limit becomes a bottleneck for export. We have faced the similar issue recently with one of our customer and the situation becomes annoying.

I would suggest to please increase this limit to at least 500MB or preferably to 1GB.

Thanks,
-Moin

 When testing, or developing, you often need to load a new version of a sourcefile in Data Management.

Right now, you cannot just replace the existing file, you need to re-specify the entity, then browse to the file, step through 2 dialogs and then you can rerun the import.

It would be way easier/faster if we can just specify a new file using all the same settings of the existing file.

Please add the following Data Entities

Sales Agreement Header

Sales Agreement Lines

These should be somewhat easy to implement since they are quite similar to the corresponding Sales Order and Sales Invoice data entities

There are currently many data entities related to Sales Tax but inexplicably there is no data entity for the basic sales tax data that is stored in the database table TAXTRANS.  There is a Tax transaction data entity however this relates to the retail module and does not hold the detailed sales tax related to Sales Invoice and Sales Order line items.

This seems like a very big oversight.