Skip to main content

Feed

Connect with fellow Trailblazers. Ask and answer questions to build your skills and network.

Does anyone know if there's a configurable input component for screen flow that can be set to only accept numbers in a format like so: XX-XXXXX-XXXXXXX? I'm trying to collect some school identification data and the ID numbers are always two digits, a dash, five digits, a dash, and then seven digits. 

 

Thanks, 

 

Jeff. 

 

#Flow  #Screen Flow

2 answers
  1. Ajaypreet Singh Saini (Grantbook) Forum Ambassador
    Today, 4:35 AM

    Hey @Jeff Illingworth, as Vuk mentioned, you can achieve this using a REGEX formula. You have to create a validation on this input component on the screen. 

    Let's say the name of the input field is "Identification Number" and API name is "Identification_Number" then your validation formula will be below:

    REGEX({!Identification_Number}, '^[0-9]{2}-[0-9]{5}-[0-9]{7}$')

    Where, {!Identification_Number} is the actual API name of your text input component's output variable.   

    Replace this with your actual input field. 

0/9000
2 answers
  1. Today, 4:30 AM

     

    as you said i done it, but it still showing the same error

     

     

    Screenshot 2025-06-19 095947.png

    as you said i done it, but it still showing the same error  

     

0/9000

Hello team ,   When i'm trying to create a training quote  which is a visual force  page  which used to work fine until  friday now  showing me this when i'm trying to create a quote  "URL No Longer Exists  You have attempted to reach a URL that no longer exists on salesforce.com.    You may have reached this page after clicking on a direct link into the application. This direct link might be:  • A bookmark to a particular page, such as a report or view  • A link to a particular page in the Custom Links section of your Home Tab, or a Custom Link  • A link to a particular page in your email templates    If you reached this page through a bookmark, you are probably trying to access something that has moved. Please update your bookmark.    If you reached this page through any of the other direct links listed above, please notify your administrator to update the link.    If you reached this page through a link on our site, please report the broken link directly to our Support Team and we will fix it promptly. Please indicate the page you were on when you clicked the link as well as any other related information. We apologize for the inconvenience.    Thank you again for your patience and assistance. And thanks for using salesforce.com!"   I don't know why i'm getting this  ?  can any one please help   

2 answers
  1. Today, 4:24 AM

    Hi @Lavanya Bolla

     

     

    The "URL No Longer Exists" error usually means the Visualforce page, record, or resource the link points to has been deleted, renamed, or moved. 

     

    Here’s what you can check: 

    Verify the Visualforce page still exists in Setup > Visualforce Pages. 

     

    Check the button or link that launches the quote — it might be using an outdated or hardcoded URL. 

     

    Recent changes: Ask your admin if anything changed in the org since Friday (e.g., deployments, page name changes). 

     

    Try relaunching from scratch, not from a bookmark or saved link. 

     

    Updating the link or restoring the missing page should resolve the issue.

0/9000

I was trying to follow the instructions on how to disconnect the playground and create a new one. I'm not sure how to move forward from here.  

I can no longer launch my playground

 

 

Screenshot 2025-06-19 110320.png

 

 

 

#Trailhead Challenges

2 answers
  1. Ajaypreet Singh Saini (Grantbook) Forum Ambassador
    Today, 4:24 AM

    Hey @Sylvia Liu, disconnect old orgs from the link below and try after some time for trailhead to provision a playground for you 

    https://trailhead.salesforce.com/users/profiles/orgs

0/9000
4 answers
  1. Today, 4:23 AM

    Hi @Lokesh Kumar

     

     

    Yes, when querying DMO in a non-default Data Space, you need to explicitly specify the data space in your request. 

     

    In your POST request to https://{{_dcTenantUrl}}/api/v1/query, add the following header:

    Data-Space: <your_data_space_name>

    Without this header, the API defaults to the default data space, which is why you're getting 404 for DMOs in other spaces.

0/9000

Hi everyone,

We're encountering an intermittent issue with the Salesforce Introspect API. For some of our users, the API occasionally fails without any consistent pattern. It works correctly most of the time, but at seemingly random intervals, it breaks — affecting only a subset of users.

In the failing cases, we receive the following error response:

{"error":"unsupported_token_type","error_description":"this token type is not supported"}

To clarify:

  • The access token we send to the /services/oauth2/introspect endpoint is a newly created token, generated immediately before the introspection request.
  • We have tried calling the introspect API both with token_type_hint set to access_token and without the token_type_hint parameter — but the error still occurs intermittently.

Has anyone else experienced similar behavior with the Introspect API? Are there known reliability issues, rate limits, or regional disruptions that might explain this?

We would really appreciate any insights, debugging tips, or best practices to improve the reliability of this integration.

Thanks in advance! 

 

@* Salesforce Developers *

 

 

#Salesforce Developer

1 answer
  1. Today, 4:21 AM

    Hi @Vikash Kumar

     

     

    The "unsupported_token_type" error from Salesforce's Introspect API usually means the token being sent is not compatible with the endpoint — and not all Salesforce-issued tokens are introspectable. 

     

    Key points: 

    Only OAuth 2.0 JWT and OAuth 2.0 Token Exchange tokens are supported by the /introspect endpoint. 

     

    If you're using standard session tokens (e.g. from username-password flow), they often won’t work with introspection. 

     

    The intermittent behavior may happen if some users are getting token types not supported by the endpoint. 

     

    Recommendation: 

    Ensure all users are receiving tokens via OAuth 2.0 JWT Bearer or Token Exchange flows. 

     

    Avoid using introspection for unsupported token types; instead, rely on token expiration handling or use identity endpoints (/userinfo, /id) if needed. 

     

     

0/9000
1 answer
  1. Ajaypreet Singh Saini (Grantbook) Forum Ambassador
    Today, 4:21 AM

    Hey @Sreeranjani Gangavarapu, can you share an image screenshot of the error instead of a doc file?

0/9000

I've a use case where I need to provide "managed package" license and 2 Permission sets to the community user on "Permission assignment"(Custom Object) record creation.

 

Also, when the record of "Permission Assignment"(Custom object) is deleted, I need to remove the managed package license and 2 permission sets.

 

I am facing an issue on the deletion part-

 

A new flow is created on "Permission assignment" object when record is deleted. When I try to remove permission set and license removal in a single flow- it gives the below error-

 

The flow tried to delete these records: 0Pa9r00000BBGG2CAP. This error occurred: MIXED_DML_OPERATION: DML operation on setup object is not permitted after you have updated a non-setup object (or vice versa): PermissionSetAssignment, original object: Permission_Assignment__c.

 

Anyone, any idea how to achieve this functionality?

6 answers
  1. Today, 4:20 AM

    Hi @Abhishek R

     

    Please find the below image of the flow- 

     

    Hi , Please find the below image of the flow- I've highlighted the 2 DML operations where the first one is deletion of

     

    I've highlighted the 2 DML operations where the first one is deletion of "UserPackageLicense" and the second one is deletion of "Permission Set Assignment". 

     

    Both of them are setup objects and still it is causing the issue.

0/9000

Error: Uncaught Error: Uninitialized EventUtils module use.  

 

Totally locks up Tableau and all on screen mouse navigation.  

Unable to swap out table name in Custom SQL     to solve:  Had to rebuild the BigQuery datasource  Had to select a new default dataset (schema) which was in a different BQ region  Had to first remove a custom SQL query referencing the dataset in the old region; replace table names to match the repointed tables in one pill; had to rebuild the second custom sql pill and rejoin it (as relationship). Important - do not drag the custom SQL pill onto the canvas - you have to double click it, otherwise you will get the 'Uncaught Error: Uninitialized EventUtils module use error  

 

@* Salesforce Developers * 

1 answer
  1. Today, 4:19 AM

    Hey @Andrew Kundinger

     

    The "Uncaught Error: Uninitialized EventUtils module use" in Tableau occurs when dragging a Custom SQL pill (especially with BigQuery) directly onto the canvas after changing datasets or regions. 

     

    To avoid the error: 

    Don't drag the custom SQL pill onto the canvas. 

     

    Double-click the pill instead to add it safely. 

     

    If switching regions/datasets, update all references and rebuild custom SQL if needed. 

     

    Rebuilding the data source and avoiding drag-drop resolves the issue.

0/9000
3 answers
  1. Today, 4:14 AM
    the error was not clerad but thank you for the help
0/9000