ENTITY STORE - Data type not participating in a column store index

(1) Share

Report

Posted on by The Martha

Hi friends,

I decided to start with the budget module. I got all the entities populated and on The Power BI.

Then I wanted to see all data for Sales and Marketing Module. I got 6 of the entities. I am only missing the Contact Person Entity.

The challenge is: the Contact Person contains a MEMO column which has a data type that cannot participate in a columnstore index.

So, I use the Target Entity in order to map the different fields and let the MEMO column out - but the changes were not saved because I get the same "CREATE INDEX statement failed error.

My question to you is: how do we omit columns (The Targit Entity) does not save the changes.

I open and closed the application - it did not help. And I see there are several types that are not supported for Column store index, so I am expecting more of these errors.

So the real bug would be.. saving the changes made in the Target Entities.. so I can publish the contact person Entity (table)

Thanks in advance

/The Martha

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

André Arnaud de Cal... 301,194 Super User 2025 Season 2 on at

Like (0)

Report

Hi Martha,

Changing the target entity mapping should do the trick. At what moments do you exactly get the index error? Is it at the moment you want to save the mapping? You are talking about "the same.... error". Where exactly do you get this error? Probably a customization on a table can cause this behavior? Have you also tried to restart the AOS?

Was this reply helpful? Yes No
The Martha on at

Like (0)

Report

Hi André,

Thanks for your answer. Actually, I get the error when trying to publish the entity. I have tried to define my entity by choosing all the felts except for MEMO.

It does not save it. So I would get the CREATE INDEX statement failed again.

Or else, when I save the mapping it seems to be working, but then it does not because I would get in the infolog that I have to omit MEMO..

Have you more or less had the same issue?

Thanks in advance

/Martha

Was this reply helpful? Yes No
André Arnaud de Cal... 301,194 Super User 2025 Season 2 on at

Like (1)

Report

Hi Martha,

I haven't used an entity with a notes fields in my tests. I have to check if I still do have an environment running with the Entity store configured to test your scenario.

Apart from this, I have done a lot with DIXF. When changing the field mappings you should explicitly hit the Save button on the mapping form. Otherwise it will not be saved.

Was this reply helpful? Yes No
The Martha on at

Like (0)

Report

Hi André,

I have saved the changes, but MEMO still comes when exporting data. I hope you have a ES scenario :)

Regards

Martha

Was this reply helpful? Yes No
Suggested answer

Munib 2,500 on at

Like (0)

Report

Hi Martha,

I believe it is a bug. You will have to raise that with Microsoft.

I had a quick look and it seems to copy over the staging table fields over but doesn't seem to to consider memo fields.

Was this reply helpful? Yes No
The Martha on at

Like (0)

Report

Hi Munib,

Thanks for your answer.

In your setup, what exactly happened? Did you also try to import all except for MEMO?

Regards

Martha

Was this reply helpful? Yes No
Jurgen van Zeeland 60 on at

Like (0)

Report

I am facing the same issue. For example when using entity HcmAccomodationType I am able to modify the target mappings (save and looking again shows it is modified) but when looking at 'Target Fields' I can see it still uses the 'Note' memo field so still receive an error.

This is tested on a clean Azure AX 2012 R3 CU10 environment (with ES installed).

I think this indeed is a bug.

P.s. Also errors about 'ModifiedBy' property on tables in the query I cannot fix. I did enable the property on the table(s) but still errors about property not set ...

Some work to do for Microsoft I assume ....

Was this reply helpful? Yes No
The Martha on at

Like (0)

Report

Yes.. not only in the tables but also in the queries.

There are tables (and queries) where we do not have the property. What could happen if we run a script to change this property in all?

/Martha

Was this reply helpful? Yes No
Anders Dahlin on at

Like (0)

Report

Any luck on this, I'm facing the exact same issue.

I can't find a way to get rid if the memo field. Even if I create a new entity the target is still the same.

Is the table created in Entity store based on the staging table or actual AX target table? In this case I'm testing with Custtable but having issues with the memo field. I don't know how to remove it.

Are you suppose to copy your tables/entities without any calculation or have you created methods to calculate values and then create entities that basically has all the data you need for your reports and values and columns calculated correctly. Or you do all the logic and joins needed for reports when you fetch data from the entity store?

Was this reply helpful? Yes No