Forum Discussion
Helper IIGrouping data in dev environment and production environment
where I come from we call this "wash me but don't make me wet".
One way to work around this is to make regular copies of the production environment into the DR environment and then point DEV and ITG to the DR environment.
Helper IIThanks for the reply.
My current set up is desktop file connect to test database only. Production database can only be accessed inside company network via on-premises gateway. Once the dataset is published from dev computer, it will then be moving through pipelines and when it reaches the Prd workspace, it has all correct connection. It has been working perfectly until the need of grouping staff together (test db and Prd db have slightly different staff list).
I hope this makes sense now.
Super UserProduction database can only be accessed inside company network via on-premises gateway.If it can be accessed via gateway then it more than likely can also be accessed via Power BI Desktop. Gateway cluster members are pretty much headless Power BI Desktops.
- hale
we are trying to limit access to PRD database directly, hence the setup. Most of the cases, we are fine, we use test database to build the schema and then once the data is deployed to the end of deployment pipeline, it can use that schema to retrieve the Prd data. Now the grouping feature of Power BI use the actual data, so we havent found a way to "dynamically" do it, hence the question. I was thinking about a staff grouping table from an Excel file so that I can have 1 for test environment and 1 for Prd. However, not sure if the grouping feature can be "dynamic" that way.
- lbendlin
where I come from we call this "wash me but don't make me wet".
One way to work around this is to make regular copies of the production environment into the DR environment and then point DEV and ITG to the DR environment.