3605980 - SAP CPQ: Default Dictionary Not Saved to Database During Bulk User Import

• When importing users via Bulk Import and the Default Dictionary column is omitted from the Excel file (or left blank), the dictionary Id is not stored in the PERSONALXML field of the user in the User table.
• Although the user record appears to be linked to the default dictionary, the dictionary ID only gets stored when the user record is manually saved in the setup or in the front-end user menu.
• This issue causes problems in the code as the PERSONALXML field is the only way to fetch a user's default dictionary.

SAP Sales Cloud CPQ

1. Prepare an excel user upload file, without the column Default Dictionary, or keep the column and leave the value blank.
2. Upload the file via Import/Export >> Bulk User Import.
3. Open the user record that was created. The Default Dictionary field is filled with US English (the tenant's default dictionary).
4. Take a note of the user id (see the url).
5. Open the script workbench and execute the provided script, entering the correct user id from step 4.
6. The result will be an XmlElement and not a dictionary id.
7. Go back to the user record and hit save.
8. Run the script in step 5 again and the result will be the Id of the dictionary US English.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

The issue is caused by a bug in the application.

The tentative fix version for this issue is SAP CPQ-2511.

3487591 - Known Issues in SAP CPQ

SAP CPQ, Bulk User Import, Default Dictionary, Database, PERSONALXML, User Table, Dictionary ID, Script Workbench, US English. , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Problem