| Created | 12/21/2022 | Updated | 02/01/2023 |
| Description | When using the new Account Search v3 subsystem, Request creation for MIRFs may sometimes fail with the following error found in the Debug Logs object: `System.TypeException: Invalid id value for this SObject type: 243209199570387973'. This is because the Salesforce Apex call instanceof Idhas a bug where it does not do a proper check whether the string is actually a valid SObject Id. Note: this issue is directly related to a Salesforce known issue https://trailblazer.salesforce.com/issues_view?id=a1p3A000000EAamQAG | | |
| Impacted Capabilities | Inquiry Management | Affected Apps | Medical Information Cloud - Lightning |
| Affects Versions | MIC V12 | Fix Version | Requester_External_ID fixed in V12.0.2 hotfix. Federation_ID__c fix still in progress. V13 |
| Steps to Reproduce | 1. Enable Account Search V3. 2. Connect an external MDM system, such as Veeva Network, as a search handler. 3. Set up the Veeva CRM MIRF integration to pull in Veeva Network Ids into the MED_Requester_External_ID__c field. 4. Have a Network ID that causes a false positive in the instanceof Id check, such as `243209199570387973`. 5. Run the Veeva MIRF Pull batch. Expected: Requests are created for all Inbound forms. Actual: Batch fails with an error in the Debug Log object. | | |
| Workaround | Delete the erroring value from the Requester External ID field. Recreate the request for the failed Inbound Forms using the "Recreate Request" button. | | |