Finance | Project Operations, Human Resources, ...

Azure Date Lake Export

(0) Share

Report

Posted on by Siopold123

Hi,

I am exporting PurchLine Entity to the Azure Data Lake (ADL) and there is an issue with the Text Field - PurchLine Name (I believe it is a Memo field).

I believe the issue is that there are & and < characters that have been copied into the field and ADL export which is using XML somewhere in the process is rejecting this.

I am trying to think what is the best , simplest and quickest way to resolve this;

Copy the data out update it appropriately i.e. & becomes &AMP or blank < becomes &lt or blank and reupdate it back to F&O

There is a lot of data so Excel and D365 Add in was going to be my method of choice but not sure that is practical or even doable

I could export the entity out via Dixf - update it and import it back in

However there is no way of preventing users (that I am aware of) from inputting this bad xml data back in.

I think the option has to be something like above whether that can be a logic app or something else to do the update maybe - just wondered if anyone else had the issue and a good simple solution

Many Thanks

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

huijij 19,811 on at

Like (0)

Report

Hi Siopold123,

Please refer to the thread to see if it helps:

community.dynamics.com/.../d365f-o-and-azure-data-lake-adl---how-to-export-data-entities-to-adl

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

Like (0)

Report

From the documentation:

The system does not export fields of type Memo, nVarchar(max), VarBinary, or Blob types into the data lake. If you choose a table with fields of these types, the system will ignore these fields and export others. We are working on enabling these special fields in the future.

You seem to be saying that the data gets exported from the entity (and the process fails later), therefore you're likely not talking about a Memo field. Please tell us which entity field you mean - the entity doesn't seem to have any Name or PurchLineName field.

Was this reply helpful? Yes No
Siopold123 on at

Like (0)

Report

Hi Martin,

Thanks for the reply. Yes I saw that MS update re Memo Fields it said that the feature was available from April 2022. The entity is Purchase Order Lines field is Purch_name - which is a text/memo field. The error though is about invalid XML characters. MS have advised to update to ADL GEN2 apparently that resolves the issue which I will try. Thanks for the help on this, Regards S

Was this reply helpful? Yes No
Siopold123 on at

Like (0)

Report

Thanks for the link Judy, doesn't really resolve my issue - MS have recommended updating to ADL GEN2 as a solution. We shall see.

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

Like (0)

Report

You must be talking about a custom field. I don't see any Purch_name field in PurchPurchaseOrderLineV2Entity and the name doesn't even meet naming conventions.

Was this reply helpful? Yes No
Siopold123 on at

Like (0)

Report

Hi Martin,

The field 'Name' on the 'PurchLine' Table

In Export to Data Lake you have the PurchaseOrderlineV2Entity which contains the table PurchLine.

However I have just found out that the export issue being encountered is from an Entity Store to Data Lake custom Aggregate Measure that has been built in the AOT, which I understand is using Purchline as part of a view and accessing the 'Name' field mentioned.

Thanks for looking into it.

Just to reiterate the issue - The Export to DL is failing on export based upon invalid data in the memo field. As I say I am coming in on the back of this. I just wanted to discover if anyone had encountered and resolved same issue with the memo field upgrade feature

Regards

S

Was this reply helpful? Yes No