Defining Business Year as per the user requirement and Year over Year option in Date Format
Hello DOMO Team,
Every user will be doing business with different set of clients, few them work with their own defined Business years. It would be definitely helpful if we have an option to predefine the business year to track their progress.
Example :-
1. Client - 1 - Business Year Starts - January to Ends - December
2. Client - 2 - Business Year Starts - July to Ends - June
3. Client - 3 - Financial Year Starts - April to Ends - March and so on...
Providing an leverage to define the Start Month & End Month will give us the an option to the user to filter their required comparison months and also have a quick calculation as per the business needs.
Best Answer
-
Thanks for the reply. I understand your usecase, and the feature you're looking for is a great idea. As you've noticed, we currently do not have such an offering. Please visit the Dojo Ideas Exchange http://dojo.domo.com/t5/Ideas-Exchange-suggest-and-vote/idb-p/Ideas. You can search existing ideas and then vote for it if it matches what you have in mind. If you cannot find it, please create a new Idea which can then be voted on by your fellow Dojo members by clicking the white arrow next to the idea.
In the meantime, you could handle this requirement by creating a new column using a Beast Mode calculation that would identify which fiscal year a particular row belongs to. For example:
(CASE WHEN `client` = 'Client A' AND `region` = 'EU' AND `Date` BETWEEN '04/01/2018' AND '03/31/2019' THEN 'Fiscal 2018' END) (obviously it would be a more complex Beast Mode than this, but this is just a basic pattern)
Alternatively, you could create a column (again with a Beast Mode) that identified which fiscal month each row belonged to. For example:
(CASE WHEN MONTH(`Date`) = '4' THEN '1' .... END) This would allow you to use the month number as a dimension, and filter/order the card in a way that gave you the desired view.
Another option would be to apply page-level filters to account for a client's specific desired timeframe. You can read more about page filters here: http://knowledge.domo.com?cid=pageanalyzer
Finally, it is possible to include logic within a dataflow transform that will create a column that indicates which fiscal year a row belongs to. This would be similar to the Beast Mode, but within a dataflow you could calculate it in relation to the current date, and with more flexibility. This can be complicated, depending on the data size of your underlying dataset.
Hopefully one of these suggestions is useful to you, and again, I would suggest submitting your product enhancement suggestion to the Ideas Exchange.
Domo Product Manager for Data Transformation (MagicETL)
1
Answers
-
Hello and thanks for your question! It's an interesting one with a lot of different potential resolutions, depending on your usecase. From what you said, it sounds like you utilize Domo to work with many different business clients, and that some of the business clients have conflicting fiscal calendars.
A couple of questions for you:
* Do you have separate pages for each business client? Or are all combined in the same page/dashboard?
* Is there a single dataset that powers cards for all clients, or do clients have more individualized datasets? How large is/are this/these underlying datasets?
With more info, I will be able to provide some recommendations.
Domo Product Manager for Data Transformation (MagicETL)
1 -
@AndreaLovesData - Thank you for the revert. Yes different Fical Years followed as per their Business Needs & not to forget Clients also work for different regions.
Replies to Queries:
* We do provide sepearate page to each business client, but their business is running in different countries. So, there is a possibility of Fiscal year defining as per the respective country regulations.
*It is a mix of both, we do have few clients whose datasets are combined & also it is the case of individual datasets too. Coming to size of dataset it varies from client. I can say that year over year the historical data increases and then this will be a task to showcase the Fiscal Year.
Summing up as per our multiple client requirements we need to showcase the data based on their respective fiscal year. Predefined column where we can mention the Start Month & End Month as per the user/client need will give more scope for analysis.
Do revert if any more details required. I see an opportunity in this aspect considering the growth of clients in DOMO irrespective of Country.
0 -
Thanks for the reply. I understand your usecase, and the feature you're looking for is a great idea. As you've noticed, we currently do not have such an offering. Please visit the Dojo Ideas Exchange http://dojo.domo.com/t5/Ideas-Exchange-suggest-and-vote/idb-p/Ideas. You can search existing ideas and then vote for it if it matches what you have in mind. If you cannot find it, please create a new Idea which can then be voted on by your fellow Dojo members by clicking the white arrow next to the idea.
In the meantime, you could handle this requirement by creating a new column using a Beast Mode calculation that would identify which fiscal year a particular row belongs to. For example:
(CASE WHEN `client` = 'Client A' AND `region` = 'EU' AND `Date` BETWEEN '04/01/2018' AND '03/31/2019' THEN 'Fiscal 2018' END) (obviously it would be a more complex Beast Mode than this, but this is just a basic pattern)
Alternatively, you could create a column (again with a Beast Mode) that identified which fiscal month each row belonged to. For example:
(CASE WHEN MONTH(`Date`) = '4' THEN '1' .... END) This would allow you to use the month number as a dimension, and filter/order the card in a way that gave you the desired view.
Another option would be to apply page-level filters to account for a client's specific desired timeframe. You can read more about page filters here: http://knowledge.domo.com?cid=pageanalyzer
Finally, it is possible to include logic within a dataflow transform that will create a column that indicates which fiscal year a row belongs to. This would be similar to the Beast Mode, but within a dataflow you could calculate it in relation to the current date, and with more flexibility. This can be complicated, depending on the data size of your underlying dataset.
Hopefully one of these suggestions is useful to you, and again, I would suggest submitting your product enhancement suggestion to the Ideas Exchange.
Domo Product Manager for Data Transformation (MagicETL)
1
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive