Great, Could you please create a playlist including 1. Create a project 2. Create a model 3. Create a submenu and table 4. Build a package 5. Deploy a package in different environments. 6.Integration with azure blob storage.
I was about to comment the same, that would be great. I have an issue, my entity only exports the data of the computed column for the company assigned to the user at the moment, I need to download the data of all the companies at the same time.
This is my first time creating data entities in Dynamics 365 F&O. I have created a customized model, then a project, and my customized table. I created the data entity, however, when I compile I'm getting errors: dataAreaId is reserved for system fields. To name one amongst several errors of the same kind. What I did just about creating the entity was also selecting the following fields: dataAreaId, createdBy, createdDateTime, modifiedBy, and modifiedDateTime. In order to solve this issue I had to delete all the objects related to the entity I created including the entity as well, then recreate the entity without selecting the mentioned fields above. I rebuild again my whole project, and this time I got no compile errors. In short, system fields cannot be used in data entities? Another question: As a prerequisite, does the table serving as the datasource for the entity must have a unique key? and the unique key must be selected in the primary index and cluster index properties for the table?
Hi. Thank you for your questions. You can add the system fields to your data entity. However you need to name them something slightly different because those names are already being used by the system fields on the data entity. So you can’t both have a data entity DataAreadID that is hidden and a field named DataAreaID that reads from the table. So you need to name the fields you create with a different name and then in the properties you can still point it to the underlying table’s DataAreaID. Same with the other system fields. In regards to you unique key question: Yes, you typically want to have a table with a unique index and add that same index to the data entity. You don’t always have to. But most of the time you will want to. I recommend looking at some of the existing data entity indexes and follow what they do.
I am trying to create a data entity for an extended table i have created (I have extended HcmWorker). But i can´t choose my extended table as data source master and it is not showing as related if i choose hcmWorker. Do you know what i am doing wrong?
Thank you Peter Ramer
for awesome video !
My pleasure!
Please keep doing more videos on D365 FO
Thank you Peter, you are the best.
@Peter Ramer Thank you so much for awesome video
My pleasure!
Shared with colleagues - great tutorial. I'm new in d365 entity world, this is huge help. Thanks!!
Thank you Peter Ramer
Please do examples with Computed columns and multiple companies. Thanks a lot!
Great, Could you please create a playlist including
1. Create a project
2. Create a model
3. Create a submenu and table
4. Build a package
5. Deploy a package in different environments.
6.Integration with azure blob storage.
Great Work... Any plans on how to develop Composite Data Entities. The Topic of BYOD is also part of Data Entities.
Thank you very much! Great help! ❤
❤ thank you
Can you post videos on Computed Column and Virtual field peter. That would be really helpful
I was about to comment the same, that would be great. I have an issue, my entity only exports the data of the computed column for the company assigned to the user at the moment, I need to download the data of all the companies at the same time.
How to publish this data entity from dev environment to test environment or production?
This is my first time creating data entities in Dynamics 365 F&O.
I have created a customized model, then a project, and my customized table.
I created the data entity, however, when I compile I'm getting errors: dataAreaId is reserved for system fields.
To name one amongst several errors of the same kind.
What I did just about creating the entity was also selecting the following fields: dataAreaId, createdBy, createdDateTime, modifiedBy, and modifiedDateTime.
In order to solve this issue I had to delete all the objects related to the entity I created including the entity as well, then recreate the entity without selecting the mentioned fields above.
I rebuild again my whole project, and this time I got no compile errors.
In short, system fields cannot be used in data entities?
Another question:
As a prerequisite, does the table serving as the datasource for the entity must have a unique key? and the unique key must be selected in the primary index and cluster index properties for the table?
Hi. Thank you for your questions. You can add the system fields to your data entity. However you need to name them something slightly different because those names are already being used by the system fields on the data entity. So you can’t both have a data entity DataAreadID that is hidden and a field named DataAreaID that reads from the table. So you need to name the fields you create with a different name and then in the properties you can still point it to the underlying table’s DataAreaID. Same with the other system fields.
In regards to you unique key question: Yes, you typically want to have a table with a unique index and add that same index to the data entity. You don’t always have to. But most of the time you will want to. I recommend looking at some of the existing data entity indexes and follow what they do.
@@peterramer Thanks, I will.
I am trying to create a data entity for an extended table i have created (I have extended HcmWorker). But i can´t choose my extended table as data source master and it is not showing as related if i choose hcmWorker. Do you know what i am doing wrong?