Finance | Project Operations, Human Resources, ...

Data Entity Export error while exporting it to BYOD from D365FO

(0) Share

Report

Posted on by BADRI NARAYANAN G

211

Hi Friends,
I am trying to export an entity named FNBI_PartitionsEntity from D365 to BYOD and i am getting an error.I have performed the following steps:
1.During export the parameter skip staging is set to /No/.
2.Full push is performed.
3.Performed the entity sync and regenerated the staging table from Visual Studio for the entity FNBI_PartitionsEntity.
4.Generated mapping and republished the data entity to BYOD.

After performing all these steps i am still facing this issue during export to BYOD.Please give me solutions for this error.Thank you.

Below is the Error during export:

Results. Cannot select a record in FNBI_Partitions (FNBI_PartitionsEntity).
The SQL database has issued an error.
Object Server Azure:
[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid column name 'CREATEDBY'.
SELECT T1.CREATEDDATETIME_,37001,T1.MODIFIEDBY_,T1.MODIFIEDDATETIME_,37001,T1.NAME,T1.PARTITIONKEY,T1.RECID_,T1.RECVERSION_,T1.MODIFIEDDATETIME,T1.MODIFIEDBY,T1.CREATEDDATETIME,T1.CREATEDBY,T1.RECVERSION,T1.RECID FROM FNBI_PARTITIONSENTITY T1

I have the same question (0)

All responses (10)

Answers (0)

Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

The error sounds unrelated to BYOD. Don't you get the same when exporting to a file?

It sounds like if the DB wasn't synchronized. I would try DB sync once more before investigating it further.

Was this reply helpful? Yes No
BADRI NARAYANAN G 211 on at

Like (1)

Report

Hi Martin,Thanks for your response.
Yes i am getting the same error during export to a excel file i.e to my local machine.I tried to sync only for the entity and the related staging table but still the same error is shown during export.

Thank you

Badri.

Was this reply helpful? Yes No
Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

I must admit that I don't know what controls whether an entity has fields like CreatedBy or not. I see some entities that have it (e.g. BenefitProgramEntity), most don't (e.g. CustCustomerEntity), and it's not clear to me what makes the difference. I think this understanding may be the key for solving your problem.

Was this reply helpful? Yes No
BADRI NARAYANAN G 211 on at

Like (1)

Report

Hi Martin,Thanks for your response.
Actually the datasource named Partitions is used for this entity FNBI_Partitions.This datasource do not have a field named CreatedBy.You are right when you said there were few entities having the field CreatedBy and some entities did not have it.It is not possible to create that field manually as well since it is a system generated field.I will try to do DB Sync and check for the issue.Please let me know if you have any other solutions on this issue , i will try them as well.The table partitions is available under system documentation in AOT.

Thank you

Badri

Was this reply helpful? Yes No
BADRI NARAYANAN G 211 on at

Like (0)

Report

Hi Friends,Can you please help me on this error.When we are trying to export this entity named FNBI_Partitions from D365 Data management to BYOD(Azure) .I have tried to skip staging,sync the DB but still the same issue exists.This is the screenshot after export by skipping the staging.Thank you.

Was this reply helpful? Yes No
Deepak Agarwal 8,598 on at

Like (0)

Report

Hello,

Did you check the property of soruce table, if createdby property is set to yes.

Was this reply helpful? Yes No
BADRI NARAYANAN G 211 on at

Like (0)

Report

Hi Deepak Agarwal.Thanks for your response.

The source table is actually a system documentation table and createdby property is set to no.The Entity named FNBI_Partitions uses a system documentation table named "Partitions"(Image attached below).

The staging table used is FNBI_Partitions and these are the properties for that staging table.Thank you.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (1)

Report

Hi Badri,

In case the Partitions table does not have the CreatedBy property enabled, the field doesn't exist and can't be used in a data entity.

Next to that, the Partitions concept is deprecated and will have only one system record in each environment. There is no business need to have a data entity for this table. Of course, you can use it for learning purposes, but then I would personally choose another table to try developing data entities.

Was this reply helpful? Yes No
Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

One thing to add is that partitions are still used by SysTest framework. This is relevant to just certain types of environments, but if you use StsTest, you can't ignore it completely.

Was this reply helpful? Yes No
Bharani Preetham Pe... 3,634 Moderator on at

Like (0)

Report

It seems to be a custom entity. As a work around, you can remove all fields in the entity and add only some set of known fields by drag and drop. Then regenerate the staging table. Do build and sync of project. Then try exporting the file from entity.

Was this reply helpful? Yes No