Error when copying alias information over
I'm attempting to copy over alias information, and received the error:
Update failed. First exception on row 0; first error: MISSING_ARGUMENT, Id not specified in an update call: []
Error is in expression '{!save}' in component <apex:commandButton> in page cnp_paas:aliasviewpage: (CnP_PaaS)
An unexpected error has occurred. Your solution provider has been notified. (CnP_PaaS)
I also received a Developer script exception email:
Visualforce Page: /apex/cnp_paas__Aliasviewpage
caused by: System.DmlException: Update failed. First exception on row 0; first error: MISSING_ARGUMENT, Id not specified in an update call: []
Class.CnP_PaaS.CreditTransactions.save: line 533, column 1
Please advise what might be causing this issue and how we can resolve it. Thank you!
-
Official comment
Hi Jillian,
Thanks for bringing this up, I discussed it with Abdul and the team. Unfortunately, it looks like the “PS-CnP-PaaS-ONLY-GrantAccountLoginAccess-CnP-Support” permission set is now empty. I believe this is related to recent Salesforce security updates and the changes they made around standard permissions.
At this point you have a few options:
- Create a new permission set with “Manage Users”.
- Go to System Permissions and scroll to the bottom where it has User Permissions.
- Check the box for “Manage Users”. When selected, Salesforce will automatically check several related permissions that cannot be unselected individually. These are admin-level permissions, so we recommend assigning this set temporarily.
- Once created and assigned to the user, they will be able to grant access to Click & Pledge.
- Coordinate with us during Live Support (depending on whether you can log in as the user experiencing the issue, or if we can coordinate with that user at the same time).
- From your system administrator account, grant access to Click & Pledge Support.
- We’ll log in, start a debug log, and then either you can sign in as the affected user to reproduce the error, or the user themselves can reproduce it while the debug log is running.
- Set up a debug log directly.
- In Setup, search Quick Find for “Debug” and click Debug Logs.
- Click New, enter the User, and for debug level select SFDC_DevConsole.
- Set it for a short time frame of only a few minutes. If the time range is too long it will create tons of useless logs.
- Once you start it, the log will run in the background til it hits the end time that you set.
- Have the user reproduce the error during that time.
- This will capture the error in the debug log. Let us know the user’s name and the time of the debug log, grant access from your system admin user, and our developers will check the logs.
I understand none of these options are ideal, but these are the current reliable paths forward. Would one of these work for you?
- Create a new permission set with “Manage Users”.
-
Hello Jillian, Good day!
This appears to be a permission-related issue. Please share your Salesforce Org ID, grant us login access, and provide the username of the user attempting to copy the Alias information.
Looking forward to hearing back from you.
0 -
Hi Abdul,
I spoke with my coworker, and they had this issue previously and said that a user must have read access to the Birthdate field in order to be able to copy over Alias data.
We are unable to grant users access to Birthdate in this org. Can you please report this as a bug that needs to be resolved? We aren't collecting birthdates, so there is no reason for access to the standard Birthdate field to be a requirement to be able to copy over Alias data.
Thank you.
0 -
Hello Jillian, Good day!
We have already addressed this, and a patch version with the fix is planned for release before the end of this week.
Please let us know if you have any further questions or concerns.
0 -
Thank you, Abdul. Where can I keep an eye out for information on the patch being available? Can we install patch releases, or do we have to request those?
0 -
We are expecting to release the patch later this week and will keep you updated as soon as it becomes available.
0 -
Thank you, Abdul.
0 -
Thank you for your patience. We’ve released the latest patch version. Please share your Org ID and grant us login access so we can proceed with upgrading your instance.
0 -
Hi Abdul,
We're now ready for you to upgrade this org with the patch. Org ID is 00D300000006fcR and access has been granted.
Thank you
0 -
Hello Jillian Adkins Good day!
We have upgraded the above instance with the latest patch version.
Let us know if we can be of any further assistance.
-1 -
Hi Abdul,
It seems this did not resolve the issue. We still have a user getting this error when they attempt to copy over Alias data:
Update failed. First exception on row 0; first error: MISSING_ARGUMENT, Id not specified in an update call: []
Error is in expression '{!save}' in component <apex:commandButton> in page cnp_paas:aliasviewpage: (CnP_PaaS)An unexpected error has occurred. Your solution provider has been notified. (CnP_PaaS)
I have asked the user to grant login access. When you look into this, please do not save any changes, but let me know what changes are necessary to resolve the issue. (I understand you may have to test the changes, as long as you change them back, that will be fine.)
Thank you.
0 -
We tried to review, but we don't have access to the instance yet.
Please grant us login access so we can review it.
0 -
Hi Abdul,
I figured you'd prefer to have access through the affected user (still waiting for confirmation from her). In the meantime, I've granted access under my user.
0 -
What permission does a user need to be able to grant access to C&P? This user only has the option to grant access to Salesforce.
0 -
Hi Abdul, I added the “PS-CnP-PaaS-ONLY-GrantAccountLoginAccess-CnP-Support” permission set to the user, but they still only see Salesforce Support as the one option for granting login access.
0 -
Hi Abdul, we set up a new perm set and that did the trick! Aleida (the impacted user) has granted access. When you look into this, please do not save any changes, but let me know what changes are necessary to resolve the issue. (I understand you may have to test the changes, as long as you change them back, that will be fine.)
0 -
Hello Jillian, Good day!
Thank you for granting access from the affected user. I have forwarded this to our developers and kindly request that you share the Alias record link or Contact link so they can review it.
Looking forward to your reply.
0 -
Hello Abdul,
This occurs with any Alias record. Here's one you can use: https://mockingbirdsociety.lightning.force.com/lightning/r/CnP_PaaS__Contact_Mail_ids__c/a3CQh00000N0zKnMAJ/view
0 -
Hello Jillian Adkins
One of our developers reviewed the affected user and confirmed it is a permission issue:
Error: Insufficient privileges – READ: Contact.AssistantName, Contact.AssistantPhone
To resolve this, please create a permission set that grants access to the above fields and assign it to the user, and then try processing the Alias record again.
NOTE: We haven't made any changes.
0 -
Hi Abdul,
Granting both read and edit access to the AssistantPhone field did not fix this issue.
Also, while making those adjustments, I noticed we still had Birthdate accessible, so I removed that since you installed the patch earlier this month. It seems the patch that was installed did not fix the issue you claimed it would fix (that a user no longer needs access to Birthdate - we also tested this as System Admin, and ran into the error without access to Birthdate). A user still must have access to the standard Birthdate field to copy over Alias data. Can you please explain why the patch did not fix that issue? (We've maintained the applicable user access to the field in the interim)
Please note this is VERY URGENT and a CRITICAL IMPACT on our users. The Birthdate field must be hidden from all users in this org.
0 -
Could you please extend the access to the instance from Admin and the user so I can have our developers review it?
0 -
Hello Jillian,
The most recent patch should have resolved the Birthdate field requirement. Can you please extend access to the Salesforce instance so our developers can determine why it is still requiring permissions for this field when processing the alias?
Thank you and we look forward to hearing from you.
0 -
Hi Rob and Abdul - access has been granted. Let me know if you need access under the impacted user as well.
0 -
Hello Jillian Adkins
It is best to grant access from the impacted user as well and extend the access duration for your user. In addition, we’ve set up a debug log, please process the alias so our developers can review the logs for further analysis.
0 -
Hi Abdul,
I am an impacted user in this case. I've just removed my access to birthdate, and I get the following error when copying over an alias - please advise (access is granted).
Update failed. First exception on row 0; first error: MISSING_ARGUMENT, Id not specified in an update call: []
Error is in expression '{!save}' in component <apex:commandButton> in page cnp_paas:aliasviewpage: (CnP_PaaS)
An unexpected error has occurred. Your solution provider has been notified. (CnP_PaaS)0 -
I also received the following email:
Apex script unhandled exception by user/organization: 0051O00000D7MHA/00D300000006fcR
Organization: Mockingbird Society (mockingbirdsociety.my.salesforce.com).
Visualforce Page: /apex/cnp_paas__Aliasviewpage
caused by: System.DmlException: Update failed. First exception on row 0; first error: MISSING_ARGUMENT, Id not specified in an update call: []
Class.CnP_PaaS.CreditTransactions.save: line 549, column 10 -
Abdul Moghni or Rob Vap - any updates? Access is granted both under my accounta and under Aleida. We are both impacted by the lack of an improvement in the patch that was supposed to eliminate the requirement to have access to the standard Birthdate field in order to copy alias data over.
0 -
I’ve forwarded this to our developers to review it. We’ll get back to you as soon as we receive an update from them.
0 -
We released the latest version last week, and our developers recommend upgrading your instance to this version, as it includes a fix for the issue.
With your permission, we will proceed with the upgrade.
We look forward to hearing back from you.
0 -
Yes, please proceed with the upgrade.
0
Please sign in to leave a comment.
Comments
32 comments