Skip to main content
SUBMITTED

Customization of System Fields

  • March 15, 2018
  • 2 replies
  • 16 views

Hi, 

in order to provide a better service with a better data quality could be necessary for our project to modify the name and behaviour of system field. 

The basic functionality are very useful but since they are field which are currently visualizable on all the created tables could be very interesting if the possibility of customization, with the necessary caution, could be available. 

Here a list of features which could be great to have available: 

1) The renaming as i.e from DW_SourceCode to XXXX_XXX or whatever;

2) The possibility of changing the current showed value such as for the mentioned field : i.e in DW_SourceCode change the "Aggregate" value to "Anything";

3) The possibility of Using the field somehow, for example with relationship or transformations. 

I hope that everybody reading this post will keep adding some features by post. 

The System Field could be a great resource, but they really need to be customizable. 

 

Thank you very much for your effort,

Kind Regards, 

Luigi Vecchione

2 replies

Forum|alt.badge.img

For (1) I think it should be standardized on Project level

For (2) The content is quite meaningless now, would be great to have some options at (a) project level, e.g. "Source Table Name" or (b) mapping level transformation, e.g. "Fixed Anything" in one mapping one and "Project Default (Source Table Name)" in another mapping to the same object

For (3) I think using system fields in transformations (as a source) is already possible

 


  • February 15, 2021

Thanks for your product feedback.
We have passed your input to our R&D department for further evaluation.
The roadmap of our product is focused on a split in ODX, MSW, Semantic Layer and Customer Portal.
With that split we will see new features and functions appear that might exceed your expectations or make the request obsolete.