Skip to main content

Feed

Conecte-se com colegas Trailblazers. Faça perguntas e responda a outras para desenvolver suas habilidades e a rede.

I launched the Developer Edition and tried to execute this module but the data under Orders doesn't show up.  

Yes I clicked All Orders. 

Yes I've disconnected and reconnected the sandbox several times.  

Yes I clicked Launch from within the Trailhead unit. 

The data does show up in another org that I found in Manage Orgs, but that one is not available to launch in this unit. I'm stuck 

 

#Trailhead Challenges

7 respostas
  1. 29 de set., 23:46

    Im having the same issue and it seems there is no response. Im stuck and I cannot progress any further until this is fixed. My agents aren't deployed as well

0/9000

APAC Command Centre — a business performance dashboard with drill-down views across Product Performance, Customer Cost/Value, and Operations & Shipping, tracking gross profit, margin, and return rate trends.

Spotify Analysis — an end-to-end music streaming analytics build. Raw data cleaned and joined in Alteryx (900K+ play events, dedup, date/boolean standardization, a custom macro), visualized across an Executive Overview and Content Performance dashboard with parameter-driven Top-N views and a custom dark theme.

Would appreciate feedback on:

  • Visual design — readability, contrast, anything that feels off
  • Chart choices — anywhere you'd have visualized something differently
  • Navigation/drill-down flow — intuitive, or confusing anywhere?
  • Anything that reads as unfinished — direct critique welcome

Links below — thanks to anyone who takes a look! 

 

APAC Command Centre -

https://public.tableau.com/app/profile/aviral.trivedi/viz/APACCOMMANDCENTRE/HubOverview

 

 

Spotify Analysis -

https://public.tableau.com/app/profile/aviral.trivedi/viz/Spotify_Analysis_17884476660320/ExecutiveOverview

 

 

#Tableau Public  #Reports & Dashboards  #Tableau Desktop & Web Authoring  #Trailhead Challenges

2 respostas
  1. 29 de set., 22:53

     Both dashboards look well thought out, especially the way the Spotify analysis handles the larger dataset and Top-N views. I’d be interested to see how the drill-down flow feels when exploring specific metrics. Overall, these are solid examples to share and get feedback on. 

0/9000

Hello everyone

I need help to complete a unit in a trailmix set up case esclation project

Unit :create an automation with flow builder

I created the automation flow process but while I create the case to taste the flow

It gives me this message

And I tried to delete the flow , but it can't be deleted too!

Any help, please?

Thanks

#Trailhead#Flow #Automation
1 resposta
  1. Eric Burté (DEVOTEAM) Forum Ambassador
    29 de set., 22:49

    Hello @Mohamed Magdy

    make sure you have well set up all lines with ID in your flow configuration items. See for example the note from within the trailhead unit : "Note: Make sure you select the Account ID option that has a Record data type, signified by a > in its row. Could you please also provide us a debug trace of your flow, or screenshots of your configured elements from within your flow ? 

    Eric 

     

     

0/9000

Bonjour je suis admin de SF et j'ai malheureusement plus les accès à la preprod / sandbox partielle. je mets mot de passe perdu mais je n'arrive pas à reinitialiser sur la preprod, comment peut on s'en sortir j'ai absolument besoin des accès  

Deuxième demande 

nous avions un ancien prestataire qui a developpé sur apex classes j'ai inactivé cet utilisateur sans avoir connaissance de l'impact mais cela a cassé l'apex qui ne se lance plus merci pour votre aide 

 

 

 

 

#Salesforce Admin

1 resposta
  1. Smitha Thomas (CIBC) Forum Ambassador
    29 de set., 22:33

    Hi @Mathilde Stanguennec

     

    Check with your team to see if anyone can access the sandbox and reset your password from your user record. They can also use a script in the Developer Console to reset your password -

    https://help.salesforce.com/s/articleView?id=000387826&type=1

    . If this option doesnt work, then create a ticket with SF Support. 

     

    For the second request, please refer to this Help article to reconfigure the scheduled jobs. https://help.salesforce.com/s/articleView?id=000385764&type=1

0/9000

In Our ORG, we have kept sharing settings for Case record private, still non-owners can see case records of other users.  

How to fix so that only owners or anyone above in Role Hierarchy  can see Case records , so far I have  checked 

1. Sharing Setting is private  

2. There is no sharing Rule, for case object  

3. There is no View All or View All Records   permission granted to the users  

4. Non-owner Users have same or Lower role in Role Hierarchy  

5. There is no Manual/Apex sharing either   

6. There is no Case Team defined in Org 

7.Non-owner users neither are account owner for the Case's account.

Why Case records are visible to  Non-owners

 

image.png

 

image.png

 

image.png

Please help me to fix it.

 

#Sharing  #Cases  #Visible Access

4 respostas
  1. 24 de set., 09:47

    Hi Neha, 

     

    A few things beyond what you've checked:

    1. Account/Contact Sharing Rules — check the "Case Access" column on those rules (Setup → Sharing Settings), not just the Account access level. This is the #1 cause people miss.
    2. Case owned by a Queue — if Owner is a Queue, all queue members see it, bypassing OWD.
    3. "View All Data" system permission (different from object-level "View All") — check Profile/Permission Sets.
    4. Confirm Case OWD literally says Private, not "Controlled by Parent."
    5. Apex Managed Sharing or a Case Assignment Rule with Predefined Case Team.

    Fastest way to nail it down — run this in Workbench Query Editor for one Case + one user who shouldn't see it: 

    RowCause will tell you the exact reason (Rule, Team, Manual, etc.) instead of guessing. 

    SELECT UserOrGroupId, RowCause, AccessLevel FROM CaseShare WHERE CaseId = '<caseId>'
0/9000

Hello! 

 

The order of bundle products on the quote is not following the bundle definition which has been defined in the product configuration in the field sequence. After turning to Salesforce they are now offering a field sequence on the quote where we can set the sequence via custom code or flow. Is anybody else experiencing this behaviour or can suggest any other workaround on this issue? 

 

Thanks, 

 

Sabine 

 

#Revenue Cloud

4 respostas
  1. 29 de set., 21:53

    you are spot on @Dominic Romanello. Based on my understanding, the PRC sequence is for Bundle structure and on Product Configurator during Quoting. However, QLI have its own Sequence field, which is not following the same bundle PRC sequence. 

0/9000

 

I see a blank page when i get into org check and when i get into profiles and permission sets I get the below error

 

 

image.png

 

I added custom label, but i get the error 

Field $Label.orgcheck__OrgCheck_ProfilePermSets_Title_CL does not exist. Check spelling

2 respostas
  1. 29 de set., 21:37
    Please send me in DM the orgid of this org. And the username you use when logining in to this org Thank you
0/9000
1 resposta
  1. 29 de set., 21:35
    Not sure if you’re able to log in successfully, but since it works when someone else logs in as you, maybe check your network or local environment configuration as well. There could be something on the browser/device side causing the issue.
0/9000

I'm working on creating a nurture email campaign for Prospects in Account Engagement, and planned to use the Engagement Studio to create the cadence... but now that there are three email builders, I'm confused on which one(s) I should be using for this and why there are so many.     1- Digital Experiences- Account Engagement CMS (Enhanced CMS) - Most user friendly, would love to use this for email campaigns. But do NOT see emails created here, in Engagement Studio. Is there a different way to build out email campaigns so I can leverage this formatting/Email Builder?    2 - "Email Templates" Tab - Limited drag/drop functionality, difficult to format - but can see emails created here in Engagement Studio.     3- "Account Engagement Email" Tab - very HTML heavy, don't love it. But can see emails created here in Engagement Studio.     Any help would be much appreciated   

1 resposta
  1. 24 de set. de 2025, 19:49

    Hi Izzi, 

     

    The 3rd option you listed is the classic email template building interface, while the 1st option is the newer lightning email template builder. When using the latter option, you have to select the option to “Activate for Automation”, which makes the email available for use as an autoresponder or a template in Salesforce Engage. For the classic email template builder you have the option to make it available for these use cases: 1:1 emails, list emails (one-off sends), Engagement Program Emails, or as autoresponder emails. 

     

    This article may be helpful:

    https://marcloudconsulting.com/development/classic-vs-lightning-email-builder/

0/9000

Creating a new workbook with a datasource with connection to MS SQL using the Tableau server GUI works fine but when clicking the "Data Source" tab the page initially loads ok but then there is a delay followed by "Unexpected Error" 

 

The error message is: 

Session ID: 71705F88A636490B90F1B1EF0D85F7C4-1:1 

Uncaught Error: Minified React error #185; visit

https://reactjs.org/docs/error-decoder.html?invariant=185

for the full message or use the non-minified dev environment for full errors and additional helpful warnings. 

 

The additional information when following the link is: 

Upon opening the above URL, here is the message ---

"Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops." 

 

I have restarted the browser, restarted tableau server, and started from scratch with a new workbook and datasource. 

 

We have many workbooks and datasources connecting to this sql server and they worked fine yesterday. 

 

All datasources to this MS SQL server are affected. 

 

 

 

Tableau Server Version: 2025.3.3 (20253.26.0206.0336) 64-bit Windows 

 

#Tableau Server

4 respostas
  1. 4 de set., 13:10

    This error was caused by login failure on AD by the Tableau service account. 

     

    Another problem that was caused was failure of Tableau to start up and then fail to either start or stop. 

     

    Both were resolved by correcting the account and rebooting the server 

     

    -Arvid

0/9000