Import Sets in HR Scope - Problem with write to tables

[Lukasz Bojara]

Hello Experts,

I have created a new table in "Human Resources:Core scope". This table extends the Import Set Row table as this one is a staging table for data import. Standard security controls have been created together with the table. The user that tries to insert the data via REST API has the following roles: web_service_admin, sn_hr_core.basic, sn_hr_core.profile_writer, user_admin, and that new role for the staging table.

The problem is that it creates empty records. The user can create records but does not have the write permissions to the fields although security controls are set up and the user has the correct role.

The same set-up, just in GLOBAL scope works perfectly and has no such problem.

Do you have an idea what is missing in this case?

UPDATE: It looks like the only role that allows to write to this table is sn_hr_core.admin, but I do not want to give that role to this user.

[Mrman]

@Lukasz Bojara please create the staging table in Human Resources :Integration scope . Extend this table from 'HR Integrations Staging'.Please try with this configuration and confirm if it works.

Please mark my answer as correct it solved your issue.

[Lukasz Bojara]

Tried this, still exacly the same problem. Records are created but empty. Not a single filed gets populated.

[Mrman]

@Lukasz Bojara can you coinfirm how is the data getting populated

[Lukasz Bojara · Accepted solution]

They are sent via ImportSetAPI, but I have found the issue. There is a *.* create ACL that was inhertied, an OOTB one in Global. I had to create a masking one [table].* and configure it for this role. Now it works.