Skip to content
This repository has been archived by the owner on Mar 10, 2024. It is now read-only.

feat: support custom field create/update for salesforce, picklists for salesforce/hubspot #2041

Merged
merged 3 commits into from
Dec 12, 2023

Conversation

lucasmarshall
Copy link
Contributor

No description provided.

Copy link

vercel bot commented Dec 8, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
management-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 12, 2023 0:01am
supaglue-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 12, 2023 0:01am

@@ -137,7 +137,7 @@ app.use((err: unknown, req: Request, res: Response<{ errors: ResponseErrors }>,
return res.status(500).json({
errors: [
{
id: req.id.toString(),
id: req.id?.toString(),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Causes issues if the json in the request body is not parsable

/* prefixed */ true
);

const result = await this.#client.tooling.create('CustomField', createParams);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We use the Salesforce Tooling API because that's what our customer uses. Using the jsforce metadata client and/or salesforce metadata API, there are some bugs. One of them is that setting a label for a picklist item doesn't work. This functionality is required by our customer, so we must use the Tooling API to support their use case correctly.

Copy link
Contributor

@asdfryan asdfryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add some documentation about which providers support picklists?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants