Most of the time, a field in a view will be called the same thing as the field it pulls from in the source table. Adding an automatic map feature based on Name would make using Map Custom View Fields a lot easier and more friendly.
IMPLEMENTED
Add Automap to "Map Custom View Fields"
Yes, very friendly and it could be extended to other scripting sections like
- Custom data selection rules
- Custom Value transformations
- Custom Conditions
- Stored Procedures
- User Defined Functions
- Script Actions
- Calculated Measures
- Add Custom Measure
- Add Custom Fields
The ability to paste a custom script into one of these areas and auto-map parameters based on name would be incredible. It might get tricky when dealing with an advanced scripts, but I would think mapping source and destination fields in the custom view mapping utility could just re-use the same logic that name-based matching when mapping tables onto one another uses.
+5Thanks for your suggestions! This feature was implemented in v20.5
Release Notes for TimeXtender 20.5.x – TimeXtender Support
+6Hi,
Just wanted to re-open this idea. The option to, for example, auto map Custom Views and Custom Value transformations would save a lot of time. The status of this idea is implemented, but as far as I know this is not available yet.
Kind regards,
Devin
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
