Finance | Project Operations, Human Resources, ...

Not able to see the data on the views after importing the license

(3) Share

Report

Posted on by CU24021359-0

Hi Experts,

We are ISV provider currently we are planning to implement licensing framework, During the testing we have observed on of our customer who imported our license key they are not able to see the data on the views. However underlying table has the data.

Just to make sure we just dropped the configuration key on the couple of views and performed the database sync then we could see the data.

Note : We could see the license is active.

Can anyone share your insights here ?

Thanks,

Guru

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (9)

Answers (0)

Sohaib Cheema 49,434 User Group Leader on at

Like (0)

Report

Hi,

I would not doubt you forgot to enable the configuration key in the system administration, where you shipped the Configuration Key along with the ISV solution's code/binaries. Is that correct ?

And what is the process for your license generation?

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

Like (0)

Report

Hi Guru,

In case you are using the ISV licensing framework provided by Microsoft, this has some caveats. Can you tell how the license was imported? Do you have only one license key and one configuration key? As you mentioned that you dropped the configuration keys, did you test the license file on a development environment or was it provided on a UAT sandbox?

When the ISV license is active, the tables are always available in the database after a sync. Views are only created when the license file is valid. When you install a deployable package including the license file, it will import the license and perform a database sync. Views should be created as part of that process.

Was this reply helpful? Yes No
CU24021359-0 12 on at

Like (0)

Report

Thanks for the response.

Hi Sohaib,

Configuration keys are enabled and this is the model deployment to the customer environment not the binary (Deployable package) because they have the customization on top of our ISV solution.

Hi Andre,

License has been imported using the AXutil command mentioned in the link (https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/isv-licensing). We have multiple configuration keys but the License code is applied only to the parent configuration key so here single license file for the parent configuration key. Currently we are testing this in the customer dev environment so we just removed the configuration key from the visual studio build and sync then we could see the data on the view.

Looking forward to hear from you.

Thanks,

Guru

Was this reply helpful? Yes No
Suggested answer

Sagar121 805 on at

Like (0)

Report

Hi,

Please check which model ID has higher precedence. For example, go to the model descriptor check ID

If there are conflicts in customizations, try installing the ISV model first, then your custom model.

If this don't help then probabaly you need to see configuraiton keys only.

Was this reply helpful? Yes No
Suggested answer

Cyrille Nembot 149 on at

Like (0)

Report

This
issue likely occurs because your views contain license-enforcement
logic that filters data when specific configuration keys are active,
even though the license appears valid. The fact that dropping
configuration keys made data visible confirms these keys are tied to
license checks in the view definitions. Possible causes include: 1) the
license missing required feature flags despite showing as active, 2)
cached or incomplete license validation during view rendering, or 3)
overzealous filtering logic in views that doesn't properly account for
all licensed scenarios. To resolve, audit the view SQL for license-check
conditions, verify all configuration keys align with the customer's
license entitlements, and ensure your license validation service returns
complete feature authorization data. The database sync may have worked
because it bypassed or reset cached license states that were incorrectly
filtering data.

Was this reply helpful? Yes No
CU24021359-0 12 on at

Like (0)

Report

Thanks Cyrille for your response,

Could you please give more details what and where to look (Like log or SQL query for views). For our ISV product we tested in the multiple environment (same tenant) where we didn't faced this issue of dropping the data from the views. Its happened in the customer tier - 1 dev environment.

Thanks,

Guru

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report

Hi CU24021359-0,

Please ignore the reply from Cyrille, as this is most likely an AI hallucination.

You mentioned that you imported the license using the AXutil tool. This can only generate a license, but will not import it. You can import it using the Microsoft.Dynamics.AX.Deployment.Setup.exe tool.

If you meant this command, then check if the license was imported correctly. You can see this on the License configuration form, tab License codes. If this is not correct, what certificate did you use? Was it a self-generated (test) certificate or one acquired via a Certificate Authority?

If the license code is imported and valid, then check if another database synchronization (after the license import) on the Tier1 environment will solve the issue. All steps are automated if you use a deployable package for importing the license in a Tier2+ environment.

Was this reply helpful? Yes No
Guruprasanna 1,078 on at

Like (0)

Report

Thanks your response Andre,

Yes we have exported using AXutil and imported using Microsoft.Dynamics.AX.Deployment.Setup.exe tool. License code status say active. Certificate issues from CA DigiCert.

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

Like (0)

Report

Hi Guru,

Thanks for the additional details. Can you also confirm you did start a full database synchronization after importing the license?

Anyway, in case the license key is not activated, the menu items having the configuration keys should not be visible in the application. When you have a valid license, the menu items become visible. For that reason, you can leave the configuration key property empty on tables and views.

Was this reply helpful? Yes No