Unsatisfied dependencies

Deployment

Business Objects

Diagnosis

Problem

You want to import a package and the import dialog says something similar to this:

Solution

This means that some of the business objects you want to import lead to unsatisfied dependencies. In other words, some aspects of your implementation refer to business objects which do not exist. For example, this can happen when a label or a type in an expression is missing.

How do I prevent unsatisfied dependencies to happen during the delivery (import)?

You can check Business Objects either individually or all at the same time.

1. Check single Business Objects for unsatisfied dependencies

Consult the "Dependencies" list: a question mark means that a dependency is missing.

2. Check all Business Objects for unsatisfied dependencies

Go to Appway Studio > Administration > Business Objects
Click on Validation
Run the validation with all severity levels selected (*).
Select "Usatisfied Dependency" as a the error type and run the validation again.

This will give you a list of all business objects containing missing dependencies.

Note:
Please note that not all missing dependencies typically lead to an error in runtime.

Could this article be better?Yes, let me send feedback

Back to Cookbook

Comments (0)

Developer is transitioning to Appway Community

All material for Appway 6 is still available here on developer.appway.com during the transition to Appway Community.

Material for Appway 6.3 and Appway 7 is available in the Knowledge Base on community.appway.com.

Note: The Community Blog, our Forum, and the Support system are available exclusively on Appway Community.

Any questions or feedback? Please contact community@appway.com

Cookbook

How Could This Recipe be Improved?

Developer is transitioning to Appway Community

See Also

COOKBOOK