Views:

Applies to Product - Power Pages


What’s happening?
Customers are unable to remove dependencies from web resources or workflows after performing migrations or customizations, resulting in error messages indicating that certain entities do not exist or that the remove option is disabled.


Reason:

  1. In the case of web resources, the application ribbon may have dependencies on a web resource that was customized incorrectly or not committed to the code repository.
  2. For workflows, this may arise from a missing workflow that was expected to be present after a migration, leading to errors indicating that the entity does not exist.

 

Resolution:
For Web Resource Dependencies:
  1. Using the tool that was initially used to make application ribbon changes.
  2. Open the solution that contains the application ribbon.
  3. Select the application ribbon from the list of entities.
  4. Within the Application Ribbon customizations, remove any changes made within Hide Actions, Commands, Display Rules, or Enable Rules that refer to the problematic web resource.
  5. Publish the changes to help remove the dependencies.
For Workflow Removal Issues:
  1. Verify that there are no dependencies or references to the workflows in the current setup.
  2. Check the configuration files to ensure no other workflows or plugins rely on the workflows in question.
  3. If the workflow is missing, attempt to delete the associated SLA or workflow from the legacy system if accessible.
  4. Use the provided links to navigate to the solution layers and attempt to remove the active customizations.