I have a validation rule created in Talend MDM model Entity to check for value exists in an element. This expression seems to not work as expected . As per the expression user should enter a value in an attribute but it allows empty values. This rule can also be implemented by turning the element to require 1:1 but as a requirement we have to implement this as validation rule. Please advise.
With your subscription solution, would you mind creating a case on talend support portal so that we can give you a remote assistance(webex session) through support cycle with priority?
We created a Talend support case and it was also taken up to product design team. They suggested that the feature is you can't implement not null check rule in Talend MDM model attribute, this has to be achieved by setting attribute are required item 1:1.
When setting 1:1 property on attribute forces the constraint to be implemented in database level , once set its hard to turn this off in the model which impacts the data in the table requiring to drop and recreate the table. It would have been nice if rule could have supported this which enables users to turn on and off the rules on an attribute.
I see Talend MDM model is very delicate doesn;t support incremental development on the model, its been suggested to develop a complete model which would take months or even years to have a complete enterprise master data model created for big companies which have 100's of applications. Hybrid MDM style is going be hard using Talend MDM.
