Unmanaged solution showing dependency on Account form but just has web resources

(0) Share

Report

Posted on by PragmaticDevs

239

I am seeing a weird behaviour. I have created an unmanaged solution and added web resources with no entities etc but when I export this solution it tells that it has dependency on fields because of an Account form which is part of my solution.

Now this form or anything from Account entity is not part of my unmanaged solution then from where is this dependency coming?

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

David Jennaway 14,065 on at

Like (0)

Report

The only reason I can think of is if the Account form had been added to the solution as a response to a prompt to add dependent objects, but without adding the Account entity. This could leave you with just the account form, but not the account entity in the solution, and, as the account form is only visible as a subcomponent of the account form, it would not show in the UI. I'd try adding the Account entity to the solution, then removing it, as this should also remove any subcomponents when you remove the Account entity

Was this reply helpful? Yes No
Suggested answer

Kokulan 18,054 on at

Like (0)

Report

Hi

Could you check the dependencies tab on the Web Resource? If dependencies are defined at the Web Resource level, you might get this warning as well

https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/web-resource-dependencies

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Hi,

This is expected if you add the webresource in any entity forms. So the workaround is to remove the JS library from the forms of account , then publish and export solution.

Was this reply helpful? Yes No
PragmaticDevs 239 on at

Like (0)

Report

Is it? In that case how people keep web resources in different solution and customizations in different solution?

To me the Form is dependent on web resource, the web resource isnt. What am I missing?

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Web resources may have published dependencies with entity forms, ribbons and the SiteMap. When the $webresource: directive is used to establish associations in a ribbon or the SiteMap, a published dependency is created.

Have a look below reference last webresource topic.

docs.microsoft.com/.../dependency-tracking-solution-components

When using the $webresource directive, Dynamics 365 for Customer Engagement will create or update solution dependencies.

docs.microsoft.com/.../web-resources

Was this reply helpful? Yes No
Suggested answer

Kokulan 18,054 on at

Like (0)

Report

Hi

I am not sure if you have seen my previous response but please see below as to why you might be getting the dependency on a field warning when you export the solution with just the web resource

In this solution below, i have just added a JS Web Resource, the solution has no other components in it.

If I export this solution, I get the following field dependency warning

I assume you are getting something like the above? if so, the reason why it's giving the warning is because in my JS Web Resource I have defined that this JS uses my custom field from Account so whenever this web resource is exported via solution, I am telling CRM to perform a dependency check to make sure my custom field is in the solution or missing component warning is given to the user.

CRM will not scan your web resource javascript or CSS to detect dependencies but it can work on the ones you define. For the above JS Web Resource, I have defined dependency as shown below

If the dependency defined is a standard CRM account field, you will not get Missing Component warning because CRM knows its OOB field and it will exist in the target environment. However, if your web resource has a dependency on a custom field or component, you will get the missing component warning

Whoever done this web resource for you, have actually done a good job of following the best practice

Was this reply helpful? Yes No
RichyRich 35 on at

Like (0)

Report

Did you ever get this resolved? I assume the replies telling you that you had setup an explicit dependency are not correct?

Was this reply helpful? Yes No