I have the following data sets:
Fact Table (Claims Information)
Fact Office Table
Entity Office Table
Not all records in the Fact_Office_Table have an Entity_Office_ID value. There should be a link between them and there is currently an IT project to back fill this information but that project is at least a year away and we have an immediate need for some BI. The data in the Fact_Office_Table is not nearly as clean as the data in the Entity_Office_Table.
What we need to do is generate a list of claims (from the Fact_Table) that belong to:
Using PP ver 1, using SharePoint. B/c using SP I believe this removes VBA from the solution. If the ONLY way to do it was with some VBA that may be a solution and we'd have to distribute the file manually
Fact Table (Claims Information)
- Fact_ID
- Fact_Type
- Fact_Office_ID
Fact Office Table
- Fact_Office_ID
- Office_Nm
- Office_City
- Entity_Office_ID
Entity Office Table
- Entity_Office_ID
- Office_Nm
- Region
- Division
Not all records in the Fact_Office_Table have an Entity_Office_ID value. There should be a link between them and there is currently an IT project to back fill this information but that project is at least a year away and we have an immediate need for some BI. The data in the Fact_Office_Table is not nearly as clean as the data in the Entity_Office_Table.
What we need to do is generate a list of claims (from the Fact_Table) that belong to:
- the FACT_Office_Ids that were selected by using slicers such as Region and Division (from the Entity Office Table) - I have this part working
- the FACT_Office_Ids I also manually select. Meaning when I use the slicers from the Entity Office Table b/c there is no relationship btwn each record in Entity Office to Fact Office - I may be missing offices I need to include in the result set. I need a way to also select Fact Office entities not selected via #1 to add to my result set. If this has to be accomplished with different slicers that is ok as long as all of the offices selected are included in the result set
Using PP ver 1, using SharePoint. B/c using SP I believe this removes VBA from the solution. If the ONLY way to do it was with some VBA that may be a solution and we'd have to distribute the file manually