Skip to main content

#Best Practices5 人がディスカッション中

Hello everyone 

 

I am developing a data visualization project using Tableau with a hotel dataset that contains booking records for city and resort type of hotels, and related data such as guest details, pricing, and cancellations, to name a few. 

 

I have drafted 4 visualizations which will eventually be consolidated into a single dashboard. 

 

Please visit the visualization link here. 

 

The visualizations were developed to answer these research questions (in the same order):  

 

Q1. How do cancellation rates differ by market segment and deposit type for City Hotel and Resort Hotel? 

 

Q2: How do booking volume and average length of stay change throughout the year, and does the pattern differ by distribution channel and customer type? 

 

Q3: What geographic patterns can be identified in cancellation rates across guests’ countries of origin, and what booking characteristics are associated with these patterns? 

 

Q4: What booking profiles can be identified based on lead time and waiting-list duration, and how do they differ by room assignment, customer type, repeat-guest status, and number of special requests?  

 

For each research question (visualization), may I request your feedback on (one or more of) based on these questions?: 

 

A. Is the chart type appropriate? If not, could you please recommend a more appropriate one along with what measures to use? 

 

B. Do any of the colors/color scheme need to be changed? 

 

C. Do you recommend mark labels? If so, for all, or for high/low only? 

 

D. Hovering over the visualization shows more details but does it look like cognitive overload? Would you recommend splitting the visualization into two or more instead? 

 

E. Do you have (any) other feedback or best practice using data visualization principles to improve this? 

 

Thank you very much in advance! 

 

#Tableau Public  #Tableau Desktop & Web Authoring  #Best Practices  #Reports & Dashboards

 

#Trailhead Challenges  #Trailhead

1 件の回答
  1. 昨日、3:14

    Your hotel booking data visualization project covers great foundational research questions, especially comparing cancellation rates across market segments and analyzing seasonal length of stay patterns. To give you constructive feedback on your draft dashboard components, your chart types for market segment comparisons and seasonal trends generally work well, though ensuring consistent color coding between city and resort hotels will help prevent visual clutter. 

     

    When presenting cancellation rates by country of origin, consider using a filled map or a sorted horizontal bar chart rather than trying to cram too many data points into a single view, as high-density hover details can sometimes lead to cognitive overload. Splitting complex geographic and lead-time distributions into smaller, focused panels will make the underlying trends much easier for your audience to digest at a glance. 

     

    Finally, to improve overall data storytelling, apply mark labels selectively to extreme high and low outliers rather than cluttering every single data point. You can also use tooltips strategically to surface guest details and special request counts on demand, keeping your primary views clean while still providing deep exploratory depth for anyone reviewing your research.

0/9000
6 件のコメント
0/9000

We want to import hundreds of forecasted opportunities for 2022 but cannot figure out the best way to import the data. 

 

Should we use the data loader? Any tips?   #NSPS #Best Practices #Data Management #Data Import #Opportunities

1 件の回答
  1. 2025年12月26日 12:30

    Yes, Data Loader is perfect for importing hundreds of Opportunities. 

     Key tips:

    • Include all required fields (Opportunity Name, Close Date, Stage, Amount).
    • Map CSV columns accurately to Salesforce fields.
    • Use Upsert with an External ID to prevent duplicates.
    • Test with a small batch first to catch errors.
    • Check success and error logs after import.
    • Automate repetitive imports via command-line if needed.

     

    This ensures a smooth, accurate, and efficient import.

0/9000

Hi Community members, 

I'm embarking on a Documentation project looking to record the various fields, objects, automation and business processes my NFP has within our customised Salesforce environment. 

 

Is there a particular format or platform that you have used to record your documentation that you would recommend? Or perhaps suggest I steer clear of?

 

(We have incomplete documentation from our implementation five years ago within Confluence and Jira but nothing that is comprehensive enough to train an incoming admin or support organisation to ask good questions.) 

 

Thanks for your time 

 

#Better Documentation #Salesforce Admin #NPSP #Best Practices

12 件のコメント
  1. 2025年8月12日 4:42

    Thank you everyone for your thoughts and the time you took to share them. 

     

    I can see our organisation using a variety of these tips to create an admin resource, an user resource and the Guidance app to distribute new features. 

     

    Thank you again all.

0/9000

I'm on a project that's at the beginning stages of building an Org that will ultimately have a large number of users whose access rights will vary greatly by user function/role.  

 

The current design is to use only 1 or 2 Profiles, and manage all of the access needs via Permission Sets and Public Groups.  Is this a recommended approach?  

 

My concern is that certain features which are dependent on Profiles - like Field-Level Security, Record Types, etc - don't support using Perm Sets and Pub Groups.  

 

Is there a best practice for determining how many Profiles an org needs, out of the gates, versus Perm Sets and Public Groups?    (FYI, the current design is to not use the OOTB Role Hierarchy either...in case that impacts this decision)  

 

Thanks, in advance!

 

#Best Practices  #Object Access  #Profiles  #Profile  #Best Practice  #Best Practices Advice  #Permission Set  #Service Cloud

4 件の回答
  1. 2025年7月10日 1:42
    What did you ultimately decide? I’m in the same situation. Very customized record types I don’t need others to see. It’s just clutter in their view.
0/9000

Did Salesforce Just Make Debugging Flows EASY? Summer 25 (short YouTube video) 

https://youtu.be/KzAs_tBPD2s

 

Formula Resources in Criteria Conditions—Yes or No? (article in flow best practice series) 

https://salesforcebreak.com/2025/05/23/should-you-insert-formula-resources-in-criteria-conditions/

 

What do you think, folks? 

 

#Flow  #New Releases  #Best Practices

7 件のコメント
  1. 2025年5月29日 18:38

    Glad you all like it, I'm quite proud of it... and we arent done yet! We have more in store.

0/9000

We currently use reverse sync in our Pardot account, meaning we bypass the lead object and sync instead with contacts in our Salesforce org. Might anyone else have their account set up this way that would be available to chat best practices? Particularly regarding reporting on campaigns and opportunities. Thanks!

11 件のコメント
  1. 2024年12月19日 23:19

    @Virginia Baaklini  I was concerned that Reverse Syncing affected other things, but that's good to know it only affects the order.  I appreciate your time and response. Thank you again. 

0/9000

I´m working in case object calling the contract lookup field to work on, but the contract object has two IDs, the salesforce contract number (automatically created) and an external contract number (text field).

 

The flow goes this way, so a customer calls to the service department, and the executives asks the customer its contract number, which is the external contract number, and once the executive digits this number on the case record type, other fields are autopopulated in the case pagelayout.

 

I mistakenly, did a lookup field in cases for the salesforce contract  number, instead of using the external number.

The customer does not have the salesforce contract number, so my question here is, can I convert the external ID from text to lookup?

#Trailhead #Service Cloud #Best Practices #Salesforce

3 件の回答
  1. 2021年11月15日 13:18

    Hi @Mariana Escalante (MX) ,

     It is not possible to change Data Types of Standard fields because they are standard and are directly provided by salesforce.com, but you can create a custom field of that data type and of this custom field you can change data type.

     

    Regards,

    Krisha Panchamia 

0/9000

Hello, I am trying to determine the best approach to identifying our competitors and reporting on them. It would not just be for relating them to opportunities. I know a standard picklist value for "Type" on the account object is "Competitor." Is that the best approach? Right now, we use the "Type" field to describe the account in more detail like whether it's a bank or private equity firm. Would adding a new record type of "Competitor" be the route to go, or should I just stick to that standard "type" field or some custom field?   

 

Also, then for tracking on the opportunity, would it be best to use a custom object or a custom field on the opportunity record?

I'd really appreciate the input. Thank you #Best Practices #Competitors #Sales Cloud #Financial Services Cloud

4 件の回答
  1. 2024年10月31日 21:53

    I've seen a lot of different ways to scale and build competitor tracking. There's an app on the AppExchange that sets up the perfect architecture to track competitors, their products, and win/loss rates with your competitors, including surfacing playbooks to your reps on the opportunities for how to talk to prospects about competitors. 

     

    Check it out here and let me know if you have any questions! https://appexchange.salesforce.com/appxListingDetail?listingId=a0NHu00000oz4xCMAQ

0/9000

As part of our implementation, we will be getting XML file from Bank which will be processed using Middleware and created as staging record in Salesforce for further processing using Batch Class.

As part of the Batch Class, we have to identify existing contact based on IBAN (like Bank Account Number). A Contact can have multiple IBAN associated with it (max 4 IBAN per contact). We are thinking of below 2 options to implement it.

 

1. Create 4 fields (IBAN1, IBAN2, IBAN3, IBAN4) on Contact record to capture IBAN and make these custom fields as external. Add query in our Batch apex to check for existing contact with matching IBAN based on these 4 IBAN custom fields (like Select id from Contact where IBAN1 = 'XYZ1" or  IBAN2 = 'XYZ1" or IBAN3 = 'XYZ1" or IBAN4 = 'XYZ1" limit 1) or. If Contact found then create Opportunity.

 

2. Option 2 is to maintain a new Object with details of each IBAN wrt. to each donor. Then in Batch class query IBAN object and search for IBAN record with matching IBAN. If found an IBAn record then tag contact id from IBAN record and create Opportunity under that contact.

 

In both options we have add additional logic to keep on updating contact or creating IBAN record based on new IBAN wrt to contact.

 

I want suggestion from the group which option is best suited in terms of best practices, considering we have 1 million contact records. If you can suggest any other option that will be great as well.

 

Thanks in advance.!

 

#Trailhead Challenges #Best Practices @Nonprofit Success Pack 

2 件の回答
0/9000