Lightning Experience Reports & Dashboards Specialist Step 1. - Challenge Not yet complete... - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
David NoeDavid Noe 

Lightning Experience Reports & Dashboards Specialist Step 1. - Challenge Not yet complete...

The custom report type 'SolarBots and Status Data' still has unwanted fields that must be removed to meet the requirements.

I have tried to rempove the five fields it says to remove, but it keeps telling that I can't. I am sure I am missing something simple. Any suggestions would be appreciated.
Best Answer chosen by David Noe
Priyanka DadhePriyanka Dadhe
Hi David,
You need to remove following fields. You can remove them from page layout or from Report type->Edit Layout:
1. kWh Roll-Up
2. Temp Roll-Up
3. Obscured Roll-Up
4. Number of Status Records
5. Maintenance Requested

User-added imageUser-added image

Thanks
 

All Answers

bhanu prakashbhanu prakash
Hi David Noe,

Mark as best answer, If it resolves !!
The issue may be report storing folder try to go through below link
https://saturn.salesforce.com/answers?id=9063A0000019cxUQAQ

let us know if it helps you and mark it best if it helps you
Thanks, 
Bhanu Prakash
visit ForceLearn.com
Priyanka DadhePriyanka Dadhe
Hi David,
You need to remove following fields. You can remove them from page layout or from Report type->Edit Layout:
1. kWh Roll-Up
2. Temp Roll-Up
3. Obscured Roll-Up
4. Number of Status Records
5. Maintenance Requested

User-added imageUser-added image

Thanks
 
This was selected as the best answer
Ajay DubediAjay Dubedi
Hi David,
Here are a few tips which can help you further.
 
1. Set Up a new Trailhead Playground for this superbadge, It will help you reduce a lot of configuration issues
2. Don’t forget to add a Value (SolarBot) into Opportunity type (Picklist Value), It is the one of the key filter value in Reports
3. Make sure all Public Groups created properly (better copy/paste the names from the superbadge details to avoid silly mistakes).
4. The Most Important thing is Some of the terminologies used not match the name as it appears in the UI (For Example Solution=Report Type, Categories=Bucket Field and etc)
5.SolarBot report folders use the naming convention SolarBot [team/group] Reports.([team/group replaced by Executive, Sales, Support, R&D]
6. Report Location and Report Type are very Important. Tip: Collect all SolarBot information, whether or not they have related SolarBot Status records
7. Pay attention when Moving reports from existing folder to New Folders
8. Get some practice for Editing Report type page layout to remove particular fields Tip: Create a dummy report type page layout and move the unwanted field into that, 
Finally, delete the page layout.

I hope you find the above solution helpful. If it does, please mark as Best Answer to help others too.
Thanks,
Ajay Dubedi
David NoeDavid Noe
Priyanka- Thanks for the screen shots and tip. Thjat was exactly iy. I was trying to remove them the wrong way.

Thanks again,

David
Priyanka DadhePriyanka Dadhe
@David Glad that it worked for you! Happy Trailblazing!
Deepali KulshresthaDeepali Kulshrestha
Hi David,
I request you to go through the following steps in order to solve the issues you are facing:
Step 1:
.SolarBot report folders use the naming convention SolarBot [team/group] Reports.([team/group replaced by Executive, 

.Sales, Support, R&D]
.Report Location and Report Type are very Important. 
.Pay attention when Moving reports from existing folder to New Folders.

Step 2:
Accounts Without SolarBot Opportunities: Create a Cross Filter as below-
.Account without Opportunity
.Opportunity type = Solarbot
.SolarBot High-Case Candidates: Use Summary field(Number of SolarBots on Account Object) which already created for you

(Number of SolarBots=0)
.SolarBot Warranty Call Sheet: Pick only Warranty Expired Accounts(Under Warranty?=False) 

Step 3:
Top Case Drivers by SolarBot Ownership-
.Report Type is Case(Standard)
.Row Summary field is: SOLARBOT OWNERSHIP
.Column Summary Field is: CASE REASON
SolarBot Status Averages-
.Report Type is SolarBot and Status Date(Custom which you have created)

Step 4:
Temperature to kWh Research-
.Make sure the Bucket field value ranges are correct
.Group by Temperature Range (Bucket field)
.Remove Details, Subtotal, Grand Total

Step 5:
SolarBot Loyalty Revenue: The formula is very Important
.Tip: IF the Sum of Number_of_SolarBots__c < 1 the Adjusted Expected Revenue is Just Sum of Expected Amount only otherwise 

.The Adjusted Expected Revenue is Expected Amount + Expected Amount *10%
.The main conditions is the opportunity having Solarbot or not
Chart is:
.Vertical Bar type

Step 6:
Sales Report Modifications:
.Add Billing state field and group it
.Use Relative Date Filter for “Next 45 days”
Support Report Modifications:
.Add Phone field and pick the chart type as Horizontal Stack bar (tick the 100%) for the first report
.Change data by week instead of by day and Pick the Chart as Line type for the second report
 R&D Report Modifications:
.Compare average kWh and average panel temperature by SolarBot model on another axis
.Place categories on the X-axis, with count on the Y axis
.Pick the Chart as Vertical bar type

Step 7:
SolarBot Pipeline by Stage:
.Report: SolarBot Loyalty Revenue
.Component Type: Vertical Bar
.Tip: Max Groups Displayed = 9
Case Drivers and SolarBot Ownership:
.Report: Top Case Drivers by SolarBot Ownership
.Component Type: Vertical Sack Bar
.Tip: Stack to 100%
Temperature and Kilowatt Hour Relationship:
.Report: Temperature to kWh Research
.Component Type: Line Type
.Tip: X Axis=Temperature Range and SolarBot Model; Y Axis=Average KiloWatt Hours
SolarBot Evangelism Countdown:
.Report: Accounts without SolarBot Opportunities
.Component Type: Gauge Type
.Tip: Careful the Segment Range Setting
Opportunity Overview:
.Report: SolarBot Loyalty Revenue
.Component Type: Lightning Table
.Tip: Set Prospecting first on the list stage opportunities

Step 8:
Color Scheme:
.Set the Dashboard Theme as Dark Except Opportunity Overview component
.Pick “Sunrise” as Dashboard Palette
Marquis Accounts:
.Create a Dashboard Filter and name it as Marquis Accounts
.Add 2 mentioned Account
.Pick account name in 1st and 5th component in instead of primary partner
SolarBot App Page: Add this dashboard into SolarBot App Page
Schedule the Report: Schedule this report to you for every Tuesday 9 a.m

I hope you find the above solution helpful. If it does, please mark as Best Answer to help others too.

Thanks and Regards,
Deepali Kulshrestha
Smita HodiggeriSmita Hodiggeri
@Priyanka -- Thanks Priyanaka.. SC helped me undertsand how to edit the layout to remove mentioned fields.
Priyanka DadhePriyanka Dadhe
@Smita
Glad to know that it helped.

 
Morgan WoodheadMorgan Woodhead
@brigitte carrabin
I am getting the same error as Benjamin but my graph is set up correctly. For some reason Very High isn't showing up on the temp but it's configured correctly. Any ideas?
User-added imageUser-added image
Raul AlonsoRaul Alonso
Superbadge
Lightning Experience Reports & Dashboards Specialist

In this case, it's impossible to delete or hide a field. I can't to move the field o unselected. What's the problem? thanks

report types fields
Hugo HiranoHugo Hirano
Hello Raul Alonso.

This problem was happening to me too. My solution was to create a new section (Create New Section button), with any name, then put those field that should remove from the page layout report (kWh Roll-Up, Temp Roll-Up, Obscured Roll-Up, Number of Status Records, Maintenance Requested), then Delete this section. Automatically it will remove those fields in this section.

This way I was able to finish the challenge 1.
Olivia Pineiro RamirezOlivia Pineiro Ramirez
Thank you Hugo! your suggestion was really helpful. For me, it was the only way to do it. 
Tami TakamiyaTami Takamiya
This thread was a life saver! I will never be able to figure out how to remove those fields without the information on this thread.  Ajay & Hugo, thanks a lot.
Archana LalArchana Lal
Hi Hugo Hirano,
I was facing the same error of removing feild. Thank you so much for tips. It really worked out for me.
Peng KuangPeng Kuang
Thank you Hugo! I couldn't figure out that could be done as a workaround solution. The user experience of this "edit layout" is painful. They definitely should make it more system admin friendly.
Eunice LeticiaEunice Leticia
Thank you very much Hugo. I had despaired until i found this.