#Trailhead Challenges2,397 discussing

Hey @Amy Wynn

, 

There are actually many ways you could do this - I'll suggest few, you can choose what suits your case. 

1. If you want the Sign up to list as Leads: 

Use Salesforce

this will generate HTML code which you can style and embed into your website. 

2. If you want the Sign ups in a custom object: 

Expose the Flow using Lightning Out or LWC.

Use an API (like REST or GraphQL) to integrate the form

with Salesforce. 

Let me know if this helps or if you have any questions. 

Regards, 

Madan

@Himanshu Malhotra

Please follow these steps and try it new playground

https://www.youtube.com/watch?v=dw2fmLFR2W8

Hello@Divyam Goyal,

• check, is there any other automation (validation Rule, trigger, flow) is activated on Account object, if any then try to deactivate 
•  If not working, then try in new fresh org, it might be the existing record causing the issues in your org. 
• Please check,

1.  https://trailhead.salesforce.com/trailblazer-community/feed/0D54V000079ScXa
2.  https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007T4NmUSAV

Hello @Sai Kiran Reddy Karingula

The problem first showed up in Platform API Basics > Use Bulk API 2.0.

I had earlier completed Quick Start: Connect Postman to Salesforce with no issues.  I then went on to complete Platform API Basics > Use REST API and Platform API Basics > Use SOAP API.  But now any attempt to get a token, use it, and try to make any API call to my playground org results in 

 [{"message":"Session expired or invalid","errorCode":"INVALID_SESSION_ID"}]

Thanks,

Matt

Hi ,

Workaround

1. Use API Version 37 or Lower

  - When making the REST API request, set the API version to v37.0 or lower. 

  - Update your endpoint to reflect this version:

Endpoint: https://{mydomain}/services/data/v37.0/tooling/sobjects/StaticResource

2. Create the Static Resource from the Salesforce UI

  - Instead of using the API, log in to your Salesforce org.

  - Navigate to Setup > Static Resources.

  - Click New to create the static resource directly through the UI. 

Not able to create/update StaticResources through tooling api with version 38.0 & above. 

https://issues.salesforce.com/issue/a028c00000zilvAAAQ/not-able-to-createupdate-staticresources-through-tooling-api-with-version-380-above

Hi ,

Workaround

1. Use API Version 37 or Lower

  - When making the REST API request, set the API version to v37.0 or lower.

  - Update your endpoint to reflect this version:

Endpoint: https://{mydomain}/services/data/v37.0/tooling/sobjects/StaticResource

2. Create the Static Resource from the Salesforce UI

  - Instead of using the API, log in to your Salesforce org.

  - Navigate to Setup > Static Resources.

  - Click New to create the static resource directly through the UI.

Not able to create/update StaticResources through tooling api with version 38.0 & above.

https://issues.salesforce.com/issue/a028c00000zilvAAAQ/not-able-to-createupdate-staticresources-through-tooling-api-with-version-380-above

Please be careful following advice provided in these answers, as they have been created using generative AI and (in addition to violating Trailblazer Community Terms) are packed with errors.

@Paul Kuriyan is mentioning that one of the queries will show all unused data extensions. How do you define unused? If this query actually worked (which it doesn't - more on this later) it would return all data extensions not used in historic sends. There can be MANY other relevant data extensions, e.g. with purchase history, ongoing data imports and many others which are necessary, but never used for sends.

You are querying _DataExtension Data View, which does not exist - and is clearly an AI hallucination. Also, you are fetching DataExtensionObjectID field from _Sent Data View. The field does not exist on this view. So it is both impossible to query all data extensions on an account, as well as get the data extensions used in sends. 

@Bryan Newman

If you delete an object/field, its API Name is also deleted.

However, in this challenge, it may be necessary to wait a few minutes after deletion for the removal to be confirmed on the servers. Try deleting it and then create an action with the required API name after a few minutes.

If this doesn't help, you will have to start everything over again.

Sincerely, 

Mykhailo Vdovychenko 

Bringing Cloud Excellence with IBVCLOUD OÜ