Quite often current data entities don’t contain all fields from the base table (for example LedgerJournalTrans table contains 200 fields, but data entity LedgerJournalLineEntity contains only 40 fields)
And that can cause a problem, because very often client wants to use some fields that are not exists in data entity and this is not possible without development.
Can you change this behaviour – by default add all fields from the base table into the data entity
Comments
To achieve the same, we need to extend the data entity. Microsoft can think to provide option to add fields in the Staging and Target tables functionally (without development) and through mapping we will be able to upload data/update data to our customized fields or un-mapped fields.
Category: Common
For datawarehouse integration I would recommend the option to sync the original source tables and all fields to BYOD. Just 1:1, so that the raw data can land/staged in the datawarehouse. It also makes the incremental load (track changes) must easier since it is only one table so the primary key is much clearer then data entities that are denormalized.
Category: Common
Additional requirement for this idea- it will be also nice to allow use data management even if data entity doesn't exist(with field mapping 1 to 1 to original table)
Category: Common
Also default WMSlocations are missing in entity Warehouses.
In case vendor or customer warehouse are necessary and many, manual update is huge
Category: Common
I second Herre's comment, think of sales table, retailsalestable, mcrsalestable...
Category: Common
For Legerjournallines there is also the requirement to have some fields from additional tables, such as CorrectedTaxAmount as this is a frequent requirement and for a customers seems to be in the same table.
Category: Common