Hello Monish,
You are right in your assessment and here is why.
In the UI, we wanted to restrain as much as possible the free text and to help the customer in choosing the right value.
While also giving more flexibility to integrating systems to push their data under the publisher that they wanted.
But we understand that it is an inconsistent behavior.
And so this is a known behavior for the product team, it is tracked internally and present in their backlog.
If you want me to communicate the reference of this internal request and to add your company as a related customer, please let me know and we will take over on ticket to share everything.
Thank you
Hi Alexia,
Thank you for the detailed explanation. Yes, please go ahead and share the internal reference for this request and add our company as a related customer. That would be very helpful for our tracking.
Thanks again for your support.
Regards,
Monish
Hi Monish,
Noted, all done :)
Monish KANTH
Hi Everyone,
We have created publishers like A, B, and C. When we try to create a master record from the UI with an invalid publisher, the system prevents the creation. However, we don’t have any validation configured in the respective stepper.
At the same time, if we try to load data through the database or API with an invalid publisher, it allows the creation and doesn’t prevent it.
Could someone clarify this behavior? I had assumed that preventing invalid publishers is handled by the product itself. Do we need to implement additional validations to block invalid publishers when creating records via DB or API? If so, how is the system preventing invalid publishers only when creating new master records through the UI?