When some atribute used on querys causes some dependency, the dependencies analisys do not identify the right query, because it appears like a generic form code.
The picture attached explains the problem.
According this question, it is the normal procedure of dependencies. However, we invite you to create it as an idea to be developed in a future release where the GUID number changes to the form name in order to find easily the correct form.
This is not an improvement idea to a next release, this is an ERROR. All othes entities and process forms appears the correct name of the form. If a Query is treaty like a form, it SHOULD appear the correct query name, not a technical name that cannot be found even in Search options.
This problem cause too dificulty to find the correct form that dependency analisys are pointing for. Besides, it do not permit to enter the form to edit on dependency analisys result screen like captured in attachment. You have to guess which form in whole application is causing the dependency.
Please ask for an emergency correction for actual realease.
Thank you a lot.
Thank you for your explication. You are right. We have identify a problem there. our product team will start to work in a solution. As soon as possible, we will write back to notify you the solution. It also will appear in our release notes in a future release.
Comments have been locked on this page!