Restrict Data Import to Group-Specific Records in Hardware table

[sattar3]

Hello everyone,

We have a requirement to allow users to import data into the Hardware table (alm_hardware), with access restricted by a custom reference field u_managed_by_group (reference → sys_user_group). We have four distinct groups. Users should only be able to import records where u_managed_by_group matches their own group.

Example

• Hardware AC team members can import assets only when Managed by group = Hardware AC.
• Hardware DC team members must not be able to create/update records for Hardware AC, and vice versa.

By Using Data Sources we need to implement this, can someone suggest how to achieve requirement?

Any scripts needs to write?

@Ankur Bawiskar @Dr Atul G- LNG @Kieran Anson 

Thanks,

Sattar

[sattar3]

@Ankur Bawiskar thanks for your reply.

I’m planning to handle group‑based hardware imports in Hardware by creating four separate Data Sources for four different groups.
Then I’ll use a single Transform Map with a Transform Script to ensure each import updates only the records belonging to its respective group. This should keep the process clean and avoid any “zig‑zag” or cross‑group updates.

Is this the right approach, or is there a better way to manage group‑specific imports in alm_hardware.

Please suggest what is the best approach and script as well.

Thanks,

Sattar

[Ankur Bawiskar]

@sattar3 

should be fine

But it also depends on customer best practices.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[sattar3]

@Ankur Bawiskar can you provide sample script for it?

[Ankur Bawiskar]

@sattar3 

I already shared sample script above

please enhance

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏