#Trailblazer Community Questions4.014 diskutieren mit

Any thoughts on why I might be getting this error when trying to login into tableau cloud?   

Hi everyone! 

I am trying to configure a new screenflow to have it's Uploaded File's name mapped into a text field.  I tried creating a Variable (Text-Collection) and added an Update Records element after the screen in an attempt to map it, but I can't get it right.   

What am I doing wrong here? 

We are seeing a repeating error from the Salesforce Slack app whenever a user posts a message in Slack. The message in the channel is delivered normally, but the author also gets an ephemeral error in the Salesforce app DM. 

Error (Only visible to you): 

There was a problem processing the Slack event MESSAGE_EVENT ErrorType: NullPointerException 

This happens on every message typed directly in Slack. 

Please advise how to stop the Salesforce app from sending these errors (configuration, scopes/event subscription, or a known platform issue). If the user sends a message from Salesforce, this error does not occur and everything works correctly;  

#Slack  #Slack Developers  #Slack Community  #Integration

PLEASE ANSWER ONLY IF YOU ACTUALLY KNOW 

WHAT YOU ARE TALKING ABOUT.  ChatGPT and Google did not help. DO NOT PASTE THAT JUNK HERE. Get Answer Leaderboard "points" on someone else's time. 

I have the System Admin profile with View All Data and Modify All Data permission.  I cannot see the New Quote button in the header on Opportunity Lightning Pages.  I have a user with a Business profile who also cannot see the button.  I have a different user with a Sales profile who CAN see the button.  In my Sandbox, I switched the blocked user to the Sales profile, logged in as him, and still cannot see the button.  When I log in as the Sales user I can see the button.  I checked different record types in different apps.  The Sales user always sees the button the Business user and Sys Admin never see the button. 

All three profiles see the same page layout for each Opportunity Record type.  "New Quote" is a custom create record action on the Opportunity object.  It works for the Sales user with no issues or errors.   

"New Quote" is an Action on the Opportunity object.  It is not a Global Action.  I checked the fields on the Action Layout and the predefined fields in the Action.  All three profiles have View permissions on all fields and none of the fields are Read Only for anyone. 

All three users are Flow users.  All three users are Marketing users.  We all have the Salesforce CPQ User (or Admin) permission set.  We all have the CPQ permission set license.  We all have the CRM permission set license. 

The Lightning Page we are seeing i the org default.  When I view the page in the Lightning Editor, I still don't see the "New Quote" button in the header.  There is no filter on the header component.  The same Compact Layout is assigned to all Record Types. 

The only CPQ plug in we have is a Product search.   We do not put Quotes in Queues.  We do not use Roles and Hierarchy.

What am I missing? 

#CPQ  #CPQGurus  #Quotes  #Opportunities  #Pagelayouts  #Lightning App Builder  #User Profiles  #Quick Actions

Hi All!  

I'm on the "Control Access to Fields" unit (

Admin Intermediate trail, Data Security module), specifically the "Set Field Permissions for Multiple Permission Sets" step, which asks me to set field-level security on the Candidate object's Job Category field. That field doesn't exist anywhere in my org (confirmed via a global Setup search), and neither do several others the unit references — Apex, C#, Hire By, Hiring Manager, and the sensitive ID field mentioned in the unit text. 

My Candidate object does exist, with fields like Current Employer, Currently Employed, Education, Years of Experience, Legacy Candidate Number, etc. — a completely different set from what the unit describes. 

For context: earlier in this trail I ran into a separate issue where the Position/Candidate/Job Application/Review objects didn't exist at all, which I resolved by installing a package referenced in an earlier community thread. That got the base objects working, but it looks like this package doesn't include the custom fields (Job Category, Apex, C#, etc.) that this later unit assumes exist — I suspect those are meant to come from manually completing "Create Custom Recruiting Fields" in the "Build a Data Model for a Recruiting App" project. 

Has anyone else run into this specific mismatch? Is completing that earlier project the right fix, or is there a different/updated package I should be using instead? Any guidance appreciated.

Thanks!