Mike_McQuaid | 2021-02-04 21:21:20 UTC | #1
I am using a SFDC data action, and it is working when using all standard fields from the Contact Object, but, if I attempt to query a custom field from the Contact Object, it does not work.
Here is an example of one working when using EMAIL as lookup critera
"/services/data/v50.0/search/?q=$esc.url(\"FIND {$salesforce.escReserved(${input.EMAIL}))} IN EMAIL FIELDS RETURNING Contact(AccountId,Birthdate,CreatedDate,Description,Email,Fax,FirstName,HomePhone,Id,IsDeleted,LastName,LeadSource,MailingAddress,MailingCity,MailingCountry,MailingPostalCode,MailingState,MailingStreet,MobilePhone,Name,OwnerId,Phone,Salutation,Title,callinid__c)\")", "requestType": "GET",
But, if I change {$salesforce.escReserved(${input.EMAIL})) to {$salesforce.escReserved(${input.Call In ID})) and change IN EMAIL FIELDS RETURNING Contact to IN CallInId__c FIELDS RETURNING Contact
(CallInId__c is the custom field in the SFDC Contact Object, containing valid data) It fails
Another note, in the one that works, I am pulling in the info from the custom field that I am trying to query in my 2nd example, the data appears in the flattened JSON, but not in the Contract Output field...
Jason_Mathison | 2021-02-05 10:54:42 UTC | #2
Hi Mike,
Could you post an export of the non-working action, along with the output it returns when it fails?
--Jason
Mike_McQuaid | 2021-02-05 15:24:44 UTC | #3
Hi Jason,
Thanks for the reply, it looks like it may be an issue querying the custom field. If I use the IN ALL FIELDS RETURNING Contact statement, it allows me to pull this back, but if I query the field directly, it fails. I think the SFDC admin needs to make that field searchable in Object Manager
Jason_Mathison | 2021-02-05 18:55:24 UTC | #4
Hi Mike,
That sounds like it could be the problem. I always suggest starting new work in a tool like Workbench to work through the kinks in a productive development/testing environment before turning it into a data action.
--Jason
system | 2021-03-08 18:55:25 UTC | #5
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 9915