MDM Error : Unauthorized delete access by user on item

[znov0087]

Hi Community,

I would like to ask if this feature is possible with our current Talend version (6.2.1):

I am currently developing a Data Model in MDM perspective. Businesses will be accessing the Data Model through Talend MDM Platform (Web UI). The Data Model will involve Location Codes in the Philippines.

Given the example:

City: Makati
Location Code: MKT
OLTName: <auto-increment>

I developed a "Before-Saving Check" Process to auto-increment a field upon creating a new record. This field will contain the location code, and the incrementing 3 digit count separated by an underscore. This field will be called OLTName.

i.e. MKT_001, MKT_002, and so on.

Since the OLTName will be automatically generated by a process, I would like to disable the field in the web UI so that users will not be able to input any data.

I have tried the following:

1. I have set the writable access to the desired role (see image below).

This enables the field, meaning, users can add data to the textbox (see image below).

Through this, I can successfully write to the database.

2. I removed the writable access (see image below).

This disables the field, meaning, users can no longer input data to the textbox (see image below).

But if I do so and try to create a new record, it gives me an error saying user is not allowed to write on the data model (see images below).

Which brings me to a conclusion, I can either:
- Give writable access to the role, but will enable the field and expose it for unnecessary input
- Remove writable access and disable the field, but won't be able to write on the data model

Question is, is there a way I can disable the field and retain the write access to the data itself?

[Anonymous]

Hello,

Are you using talend open studio for MDM or subscription solution for MDM V 6.2?

Best regards

Sabrina

[znov0087]

Hi Sabrina,

I am using Talend Studio for MDM Platform v 6.2.1.

Regards,

Emil

[znov0087 · Accepted solution]

After exploring the back end database, I now achieved the feature that I wanted. What I did was to remove the writable access to that certain field, and then I performed the writing process directly at the back end database. Technically, I still get the error since I have no writable access for my Talend MDM user, but another process writes it for a second time using a back end database user with write access.