关于rohithnarayan

rohithnarayan · ‎12-14-2021

Thank you @rob_marshall and @JaredDolich for the quick inputs. Based on inputs, I have the following Since the Source data is coming as Text, I cannot avoid Text format. I did assign values to each color and did have a formula Summary for a new field which would be exposed in dashboard with the formula below. Value Assigned:- IF Text Input = "Green" THEN 1 ELSE IF Text Input = "Yellow" THEN 2 ELSE IF Text Input = "Red" THEN 3 ELSE 0 Final Color - Export IF Value Assigned >= 0.5 AND Value Assigned < 1.5 THEN "Green" ELSE IF Value Assigned >= 1.5 AND Value Assigned < 2.5 THEN "Yellow" ELSE IF Value Assigned > 2.5 AND Value Assigned < 3.5 THEN "Red" ELSE "Black" Kindly confirm if this logic holds good with huge data.set. Conditional formatting might not 100% match to its value, but I think its the nearest what we can achieve.

rohithnarayan · ‎12-14-2021

你好,要求:父母应该有verage color of its children. I have an Indicator(Red , Yellow, Green) coming as a Text input from the Source. The requirement is to roll up to its immediate parent and its final parent subsequently based on the average color as per the children hierarchy. Kindly let me know how to we aggregate / average text values. Thank you very much in Advance!

rohithnarayan · ‎10-18-2021

Hello, Do we have any work around right now to have the Copy Down / Across in new UX as of now? Kindly let me know.

rohithnarayan · ‎06-05-2020

Yes , It gives DEV and UAT in the drop down in Prod. We need to select UAT. If you select DEV ---> Prod , it works but later on , when you create one more tag and push to UAT and then feel to take it to Prod from UAT, it will fail bcos UAT and PROD will not be in sync. We need to be careful what we are trying to achieve in each model. DEV is for development with less data UAT is for testing and Sign off with Prod sample data. Prod is for Actual Production.

rohithnarayan · ‎06-05-2020

My vote goes to ALM. Initial setup might be tough but its worth so that you could do lot of testing before the code is in PROD HUB in order to ensure there is no corrupt data loaded and fool proof imports from various Sources. HUB is the Source of Truth to all Planning models and we should care them with high respect

rohithnarayan · ‎06-05-2020

As per your query, you already have DEV and TEST. If all the testing is complete and user has given the green signal to deploy, Copy the TEST to PROD workspace(If it exists) or copy TEST to PROD in same Workspace and rename as PROD.(May be you need to delete the data in PROD after deployment - depends on the project) Make a small change in DEV and create a revision tag. Move the Changes to TEST from DEV. Next Move the changes from TEST to PROD model and you are all set. DEV-- >TEST ---> PROD. Hope it helps.

rohithnarayan · ‎06-06-2019

Just Click on the Top Right of the Dashboard which will enable the Dash in Edit mode and any changes made here to any modules or alignment you can either save or Discard , again on the Top Right of the Dash.

rohithnarayan · ‎06-06-2019

Always use CODE for Insert / Update the data in the List. CODE will not change compared to Name / Duplicate names.

关于rohithnarayan

Re: Anaplan Roll up for Text Fields

Anaplan Roll up for Text Fields

Re: Copy Across and Down on right click of an inpu...

Re: ALM设置开发测试到Prod

Re: Single or Multiple Data Hubs with ALM?

Re: ALM设置开发测试到Prod

Re: Saving changes to selections on a Dashboard

Re: Import Error

Re: Anaplan Roll up for Text Fields

Re: Anaplan Roll up for Text Fields

Re: Anaplan Roll up for Text Fields

60 Tips for Acing Your Anaplan Interview