When running the "Find unused fields" function, Tx may find and report "false positives" - that is fields that the developer is using in custom scripts. Removing these fields will yield errors when executing the project (this happens even if the tables and fields involved are all referenced in the script).
It would be good to be able to manually flag a field as "in use" to allow the "Find unused fields" function to ignore them.
Hi Jan, thanks for the reply.
The variant used in the parameterised custom sql step is of "Field name" type. Is this wrong? I've tried to set it as "Field name with valid table" - which produces the same behaviour. I would email screenshots to you if you are interested.
It could also be a field that timeXtender does not know is used. Like a stage database being used as data source in another stage in the same project.
Hi Rasmus
Thanks for submitting your ideas. Your continued feedback on our product is very important to us. And so is your engagement in our community.
I have passed your input to our R&D department for further evaluation.
I hope you have become familiar with the manual mapping of fields for vies and scripts which was released in version 19.2.x
It's difficult to identify whether the field is being used in another project, but at the time of this posting, the current product roadmap is focused on a major evolution in foundational pieces of our software including splitting the development into ODX, MDW, Semantic Layer, and User Portal. With this evolution, we will continue to see incredible innovation in the product that may exceed your expectations or make the need for this feature obsolete.
If you have any questions or would like to discuss further, please reach out to me or the dedicated TimeXtender Solution Specialist in your region.
Thanks!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
