Microsoft Dynamics AX (Archived)

EDT Configuration Key property unavailable for edit

(0) Share

Report

Posted on by JayAXDinamics

130

Hello guys,

Does any one faced before with problem to change Configuration Key property on EDT?

AX version is 2012 R3 CU10.

It is accessible to change Configuration Key property on tables but it does not on Extended Data Type.

All I have noticed our development license has "Enable license code authoring and editing" option disabled.

Could any one suggest some solution to test?

Thanks in advance!

6114.Example1.png

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Tommy Skaue Moderator on at

Like (1)

Report

I see the EDT is without ConfigurationKey in R3 CU9.

The SysLicenceCodeEditing seems to be unrelated, though:

technet.microsoft.com/.../hh456312.aspx

Was this reply helpful? Yes No
Dauvis 170 on at

Like (1)

Report

I noticed that many of the sys/syp level objects disallow the changing of the configuration key. I suspect that it is there to enforce licensing restrictions.

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (1)

Report

Yes. This is by design.

So either this was added in SYP with CU10 or something else is going on. :-)

Was this reply helpful? Yes No
Douglas Noel 3,905 on at

Like (1)

Report

Hi Jayl,

Here is a hardcopy of a clean R3CU10. The configuration key comes from the base EDT but is not shown here

one question? How did you archive to have this Foundation EDT in another model? MWMParking????

regards

Douglas

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

Like (1)

Report

@Douglas: An easy thing to do. Simply modify the EDT - the change will be done in your active model in the current layer. It doesn't means that it disappeared from Foundation in SYS - you're simply looking at a different layer.

Was this reply helpful? Yes No
JayAXDinamics 130 on at

Like (0)

Report

Thank you all for fast replies,

I am doing upgrade from AX 2012 FP CU3 and client have modified EDT on source system as fallows:

and origin EDT was with empty Configuration Key property.

I have no idea how client managed that changes to implement and I have transfer it some how on CU10 :))

Was this reply helpful? Yes No
JayAXDinamics 130 on at

Like (0)

Report

Hi Douglas!

Thank you for reply, but I have tried another EDT from Foundation model and result is the same even for base EDT

Was this reply helpful? Yes No