web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Configuration key not ...
Finance | Project Operations, Human Resources, ...
Unanswered

Configuration key not enabled for the entity error when adding a custom data entity manually

(0) ShareShare
ReportReport
Posted on by Retha 1,455

Before upgrading to V10.0.15, when we added a new custom data entity, we just ran the Refresh entity list on UAT and production and it pulled in the new data entity. We also have a data warehouse where we have  Data management projects that export data to the data warehouse instead of to Excel.

Since upgrading to v10.0.15, we can't run the refresh data entity list anymore because it breaks the data warehouse. It is because prior to v10.0.15, when exporting to a data warehouse, it automatically looked at the configuration keys turned on and only export the fields that have a configuration key enabled. Now with v10.0.15, it broke the data warehouse with the data entity refresh because it is not looking at the configuration keys anymore. We had to manually go and remove all the fields for which we do not have the configuration key enabled.

So, now we are stuck in that we cannot run the data entity refresh anymore. How can we add manually now a data entity without getting the error "Configuration key is not enabled for the entity"

I have the same question (0)
  • zhifeng Profile Picture
    zhifeng on at
    RE: Configuration key not enabled for the entity error when adding a custom data entity manually

    Hello Retha,

    Do you mean refresh entity list broken your existing export project?

  • Retha Profile Picture
    Retha 1,455 on at
    RE: Configuration key not enabled for the entity error when adding a custom data entity manually

    We have projects that export to an Azure SQL DB that is our data warehouse.  Since v10.0.15, when these projects are run after a refresh of the entity list, the data warehouse breaks because all fields are pushed instead of only the ones for which a configuration key is enabled like it used to be in prior versions.

    So unless the user wants to delete fields every time after a data entity refresh, we cannot run the data entity refresh.

    There are a lot of entities, standard and custom that are used to push data to the data warehouse. So it is not an easy task to clean up after a data entity refresh.

    I don't know if the error happens on the project side when the data is pushed or on the Azure SQL DB side. The user just stated that the data warehouse broke and that she had to manually delete all the fields. But it definitely now runs a different process for pushing data to the Azure SQL DB than when it pushes to a file like Excel.

  • Retha Profile Picture
    Retha 1,455 on at
    RE: Configuration key not enabled for the entity error when adding a custom data entity manually

    We are using this feature: docs.microsoft.com/.../export-entities-to-your-own-database

  • Retha Profile Picture
    Retha 1,455 on at
    RE: Configuration key not enabled for the entity error when adding a custom data entity manually

    If you read this link: www.d365ug.com/.../byod-tips-tricks-1 and scroll down to publishing data entities, it mentions that one can delete fields under the target entities that you do not want in the BYOD. It is a 2018 document, so not all might still be relevant.

    The data entities being pushed to the BYOD are also used in regular exports  to Excel. So removing field mappings isn't an option.  Prior to v10.0.15 upgrade, we didn't have the problem of needing to remove mapped fields. Now we have to remove mapped fields.

    After a refresh of the entity list, it puts all the fields back into the mapping and one has to manually go remove the mappings with disabled configuration keys again.

    For example, looking at Purchase Order Confirmation Headers data entity, we do not have the field configuration key "BankDocument" enabled. I did an export but exported only to Excel and the field: BankDocumentType was NOT exported. It isn't in the Excel file. this is correct because we do not have the configuration key enabled. Prior to v10.0.15 this field also would not have been pushed to the BYOD Azure SQL database.  However after the upgrade to v10.0.15 it now tried to push this field to the BYOD and it fails because of this error:

    One or more configuration keys are disabled in the data entity , 'Purchase order confirmation headers'. A field is available to be used in data management if the configuration key of the field, its table and its data entity are all enabled

    So, now we have to manually go in and delete all the fields from the data entity that has no configuration key enabled. We have to do it every time when the Refresh of Entity Lis tis run. This is ridiculous.

    So how can I get past the refresh of the entity list when creating a new custom data entity and adding it manually or adding a new field manually? It doesn't want to enable the configuration key for the entity and thus the entity cannot be used in data management.

  • Tony zhong Profile Picture
    Tony zhong 897 on at
    RE: Configuration key not enabled for the entity error when adding a custom data entity manually

    Hi,

    I'm sorry, but how to enable Configuration key ? Is by assigning (key in) the key in its property means it is enabled ?

    And do we need to key in each fields of the data entity or is it enough on the Data Entity property it self.

    Thanks in advance,

  • zhifeng Profile Picture
    zhifeng on at
    RE: Configuration key not enabled for the entity error when adding a custom data entity manually

    Please refer below article how to enable configuration key.

    docs.microsoft.com/.../maintenance-mode

  • Retha Profile Picture
    Retha 1,455 on at
    RE: Configuration key not enabled for the entity error when adding a custom data entity manually

    I in the end added a custom button to form DMFEntity. the user then clicks on this button after adding the data entity manually tt he grid. this button ran then an extension on class DMFDataPopulation to apply 2 of the methods (EnableEntity and setEntityConfigurationKeys methods) to a single data entity that the Refresh data entities list function would have done.

    I had to duplicate a lot of the code because the methods I needed to extend or call were either PRIVATE or INTERNAL.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 1,850

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 795 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 519 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans