search

microsoft / bc2dataverse

Integrate Business Central to Dataverse in a low code way
MIT License
22 stars 5 forks source link

setting the base ID #5

Open kine opened 1 year ago

kine commented 1 year ago

When generating the proxy table, there is no way to set the base id to be used for the field IDs of the proxy table. They are numbered independently on the ID entered for the new proxy table.

DuttaSoumya commented 1 year ago

CC: @onbuyuka

Let me try to understand you better @Kine. Suppose the dataverse table has 3 fields and you provided invoking the proxy table generator with baseID 50000, then you expect that the 3 fields have IDs : 50001, 50002 and 50003, instead of 1, 2 and 3? Why do you see this as a limitation?

kine commented 1 year ago

The problem is, when someone extends the existing standard tables like Contact (it means, the tool will find some table in the symbols and will generate the table ext.). The app will create table extension, but the field are numbered in MS id range, not ours range. I need to renumber them afterward.

Current numbering is not a problem, when we are generating proxy for new table.

Sorry that I was not clear in this.

DuttaSoumya commented 1 year ago

Got it! Thanks @kine. Field IDs can be named 1, 2, 3 etc... they would still compile in the PTE (for example, see this PTE table). Therefore the renumbering of field ids to the partner object IDs appears to be an optional step to deploy the app. Thanks for the suggestion- however the workaround seems to be clear and easy, and one- time for each table.

kine commented 1 year ago

Yes and no.

Yes, it is not problem, when the table is created as a product of the run. No, if TableExtension is created, because in this case, the IDs must be in the partner range. And one time renumber is not so good, when you need to update the TableExtension again when some change was done on the Dataverse side.

But yes, I can fix it manually, but every time I run it to refresh the schema, I need to renumber them again.