Flag attributes in Subscriber Dimension
2 posters
Page 1 of 1
Flag attributes in Subscriber Dimension
Hi,
Our business users want to see some flag attriubutes (like exclusion flag, eligible for campaign flag etc) in subscriber dimension.
For example, If the tariff plan of the subscriber is X and that subscriber has the property Y then exclusion flag of that subscriber will be set as 1.
Or if the subscriber has the product Y and has no unpaid bills then it will be flagged as "eligible for campaign".
Those flag values can be queried from subscriber products and business users can have these flag values while creating the report query. Business users do not like to generate complex queries and want to see every analytical result as a flag in customer or subscriber dimension. I don't want to model this kind of requests. Can I take your opinion on this case?
Our business users want to see some flag attriubutes (like exclusion flag, eligible for campaign flag etc) in subscriber dimension.
For example, If the tariff plan of the subscriber is X and that subscriber has the property Y then exclusion flag of that subscriber will be set as 1.
Or if the subscriber has the product Y and has no unpaid bills then it will be flagged as "eligible for campaign".
Those flag values can be queried from subscriber products and business users can have these flag values while creating the report query. Business users do not like to generate complex queries and want to see every analytical result as a flag in customer or subscriber dimension. I don't want to model this kind of requests. Can I take your opinion on this case?
umutiscan- Posts : 51
Join date : 2010-11-26
Age : 44
Location : Istanbul, Turkey
Re: Flag attributes in Subscriber Dimension
I can understand where the business is coming from, but flags are not the way to go. The types of analysis and levels of classifications can be endless. One way around this without too much work is to let them create lists of keys. This would allow them to establish populations for particular purposes based on some set of criteria that they may dream up.
As far as easier querying goes... find a proper front-end tool that suits their use case. Don't put it upon yourself to handle everything in the model, it becomes impractical very quickly.
As far as easier querying goes... find a proper front-end tool that suits their use case. Don't put it upon yourself to handle everything in the model, it becomes impractical very quickly.
Re: Flag attributes in Subscriber Dimension
What do you mean with "let them create lists of keys" ? Do you mean letting them to load list of customer numbers or subscriber numbers and to use those lists in their queries?
umutiscan- Posts : 51
Join date : 2010-11-26
Age : 44
Location : Istanbul, Turkey
Re: Flag attributes in Subscriber Dimension
Our reporting tool is BO. So not modeling this kind of flag values, adding a sub query or join when that flag attribute is dragged in the report would be a good choice for this case.
Your comments are very helpful, thank you.
Your comments are very helpful, thank you.
umutiscan- Posts : 51
Join date : 2010-11-26
Age : 44
Location : Istanbul, Turkey
Similar topics
» Usage flags in subscriber dimension
» dimension table design question for around 100 attributes and higher level calculated attributes
» Current Flag in a Dimension
» Dimension Attributes
» Dimension Attributes and Fact attributes storing same data in multiple data marts??
» dimension table design question for around 100 attributes and higher level calculated attributes
» Current Flag in a Dimension
» Dimension Attributes
» Dimension Attributes and Fact attributes storing same data in multiple data marts??
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum