Exporting and importing many user profiles at once in IFS Cloud: what the community has tried

Unverified: there is no accepted answer, and the original poster ended up handling profiles one at a time. The community suggested these approaches:

1. Back-end PL/SQL script (suggested by aslane): call client_profile_handling_svc.do_export_profile_action to generate the profile nodes, then client_profile_node_api.generate_xml_data_for_node to get a blob. Convert the blob to a clob and write it to an XML file with dbms_xslprocessor.clob2file. To import, reverse the process: read the file into an xmltype and pass it to client_profile_node_api.import_xml_data.
2. REST automation (described by REOGIRARD, tooling not shared): through the ClientProfileHandling projection, query ClientProfileSet and take the PROFILE_ID values from the keyref field, call ExportProfileAction per profile, and use the returned request key to download the XML (one file per profile). For import: initialize an XmlVirtualSet, upload the XML through the FileData endpoint as octet-stream, create a temporary LOB through FndTempLobs, attach the profile selection, run ImportProfileAction, then clean up the temporary virtual entities. Each call needs a bearer token and the x-ifs-content-disposition header.
3. Quick Report export (suggested by timsides): select * FROM CLIENT_PROFILE_NODE_FULL, then shape the output into XML (for example in Excel). Do not include state, OBJ_VERSION, PROFILE_ID, PROFILE_NAME or OWNER as elements. He doubted this imports at user level, but said sections such as bookmarks and table view layouts can be imported into users' profiles.
4. Database export plus custom import script (PhillBronson), split into manageable chunks.
5. GTVMARBIE said multi-select export is locked in core code and can be unlocked; export then produces one file per profile, and import still has to be done profile by profile.

Conflict: REOGIRARD said multi-user profile import became unnecessary because IFS Cloud 24R1 has that feature, but the original poster reports the limitation on 24R1 and another member reports it on 25R1. Check your own release before relying on either view.

Prerequisites and limitations None of these approaches is confirmed as tested by the asker; they are community workarounds, not an official IFS feature. The PL/SQL and REST routes need database or API access with appropriate permissions and should be tried in a non-production environment first. Unlocking multi-select in core code would be a core modification. Whether 24R1 includes a native multi-profile import is disputed in the thread.