For BG, which column should I use for mapping, the API Name or Help Text ?
The help text is just a description or any data restrictions on the field itself
Like some are picklists with certain choices.
okay. So I would use the API name then.
sounds good. I also see some dup in the questions.
But some of those fields have restrictions and if so, it will be defined in there
You bet don’t hesitate to ask.
Hi Darrell, can you give us the case type for BG please?
Here's what it looks like in the doc for your reference: "caseType": "a03Hn00000vwHQeIAM",
yes that ID corresponds to the Salesforce case type
so we should use the above case type that's mentioned on the doc?
I think the doc is for the AFFF not for the sexual abuse tho
Please check the source also. On the doc it's stated as "source": "a0YHn00000UUkzSMAT"
I think we should use the ones in the sample. I can’t access their org in order to look up the ID number to see if it corresponds to the correct.
Source should be fixed though because we will always be the source for them so I think they set a fixed ID.
I see. But as I said the example doc is for AFFF if im not mistaken.
I think they just forgot to change the title on the example document frankly. They have to create all of this meta-data for each new case type and send us a document like that. I completed AAAF for them a few months ago. When I asked for the new documents, I think they just didn’t change the title. However, I think we should Default to whatever it is in that sample json.
Test sent successfully on our end. Please let me know how it's on your end?
{"data": {"name":"MAT25010337519","externalId":"BRIOTEST-2025-01-03 22:55:50zI9DD","id":"a0LPY000008TgC92AK","abuse":[{"externalId":"BRIOTEST-2025-01-03 22:55:51YnHsX","id":"a3JPY000000Ab4j2AC"}],"client":{"externalId":"BRIOTEST_623092","id":"001PY00000TQaLrYAL"}}, "success": true}
Nice!! I'm actually not the client. We need to email Chris @ BG and see if 'a3JPY000000Ab4j2AC' was created and confirm that related records (e.g., abuse and client) have been created or updated as intended.
Hey Darrell, on #278 do you have a full question on column H?
No I have the same document you do. What’s the issue? I don’t think they provided help text on every row.
Are you saying you’re having trouble matching it to a field on the questionnaire?
yeah, I was wondering if you have the question in full, as the question on column C is in short form
I only have this same document the client shared with us. Can it be interrupted from the sample json?
nvm, I thought you are the one who prepared the doc. you meant Interpreted right? I have tried but wanted to make sure.
yeah interpreted sounds much better 🙂 No I didn't create this. It all came from the client.
🙂 I see... thanks man for the quick reply.
Hey @Darrell, we were trying to do this contenttype = mimetypes.guesstype(attachment[0])[0] file = { 'Id': intakelead["externalid"], 'filename': attachment[0], 'externalId': intakelead['leadid'], 'shortDescription': 'Retainer' if 'SignedContract' in attachment[0] else '', } response = requests.post('https://baileyglasserllp.my.salesforce-sites.com/customapi/services/apexrest/brioapi/SingleFileWebhook', params=file, headers={'sforgid': 'BRIOTEST', 'apikey': key, 'Content-Type': contenttype}) on the main.py but we are getting this Bailey Glasser: [["665129-Ronald2 Davit3-IntakeForm.pdf", "<Response [400]>", "{\"error\": \"id is missing\", \"success\": false}"]] error and Im wondering if you have an idea as to why this is erroring out
It sounds like the Apex REST endpoint is expecting to receive an id here. Maybe the Intake ID to relate the document?
or.... Depending on the Apex code, it may only be looking at the request body, possibly as JSON, and ignoring query parameters. I cant remember what that endpoint looks like. Chris can put us in touch with the developer BRIO
Also Content-Type If you’re attaching a file, you might need a multipart/form passing the file data separately in the files parameter
I think it would be great if the developer BRIO can give us an idea
Actually we forgot to send the file. We just fix that and we will try testing it. Thanks! you made a good point on that.