Jump to content

Recommended Posts

Posted

Hi Everyone,

 

As I understand it, to get SIMS data into Power BI you have to schedule reports to output to CSV/Excel and then use a gateway/sharepoint to make them BI data sources. Is that right/the only way?

 

Is there a way of setting that up that's compliant with GDPR?

 

Ed

Posted (edited)

nope.

 

command reporter dumps to csv and powerbi desktop can open them (in the most basic usage).

 

Publishing to the web is the dodgy bit.

 

The real trick is NOT to export identifiable pupil/staff level data into powerbi - then we're playing with summary information and all is well.

 

GDPR is really no more complicated than good data security - if you don't need it then don't pull it.

Edited by bobsmith
Posted (edited)
Why are you publishing to web?!?

 

Personally I'm not sharing to the web - but if you want to share it don't you have to publish it to the web? (even if you do it through your own office365 tenanacy)

Edited by bobsmith
Posted
Publishing to the web is a route that creates a public facing version of your report to the web. If you Publish from the power bi desktop it appears within a workspace of your choosing and is not public facing.
Posted

Nope. In PowerBI Desktop you publish - that goes to your PowerBI\Office365 tenant. All nicely encrypted etc. One you've done that, you can publish to web.

 

Publish to web should be switched off on your tenant. If you do actually want to publish something to web - highly recommend creating a second tenant.

 

Wonder if it's worth a EduGeek PowerBI \ session?

Posted
Nope. In PowerBI Desktop you publish - that goes to your PowerBI\Office365 tenant. All nicely encrypted etc. One you've done that, you can publish to web.

 

Publish to web should be switched off on your tenant. If you do actually want to publish something to web - highly recommend creating a second tenant.

 

Wonder if it's worth a EduGeek PowerBI \ session?

 

It does worry me that some schools may have published to the web without realising the consequences..

Posted
You can also link directly to the SIMS DB with Power BI and miss out the middle man (Excel). Are school publishing to the web by accident as they have not purchased the BI license to just publish internally?
Posted
You can also link directly to the SIMS DB with Power BI and miss out the middle man (Excel). Are school publishing to the web by accident as they have not purchased the BI license to just publish internally?

 

Won't Capita crap themselves if we link straight to the DB?

Posted
Won't Capita crap themselves if we link straight to the DB?

 

They'll prob point out you've just void you're support and made your school unGDPR compliant as SIMS security wasn't decided for you to hook directly into the db. So I'd think SLT \ governors would be the ones crapping themselves :D

Posted

Only if you were publishing to the web which is a really bad idea regardless of where you are grabbing the data from.

 

If you are 'worried' about support then its a simple task to create a shadow SIMS_Reporting.mdb (DB) and automate the backup/restore routines from live and point Power BI to this warehouse.

Posted
If you are 'worried' about support then its a simple task to create a shadow SIMS_Reporting.mdb (DB) and automate the backup/restore routines from live and point Power BI to this warehouse.

 

MDB? As in Access DB??

Posted

 

They'll prob point out you've just void you're support and made your school unGDPR compliant as SIMS security wasn't decided for you to hook directly into the db. So I'd think SLT \ governors would be the ones crapping themselves :D

 

Was this really true? I was never sure if it was a myth. Pointing PowerBI directly at the DB and setting up an on-prem gateway for the workspaces to refresh from is absolutely the right way to do it.

Posted

Yes, Microsoft advise is to point the PowerBI gateway at a SQL server. 100% Agree. Except that's best practice. Back in the real world. You've just bypassed all the SIMS security. You can't go into SIMS, create a user account (which creates a SQL user), limit the access then use that account in the PBI gateway. For starters the password won't work, then you'll find once you figure how SIMS mess around with password you don't have any permissions to the data. So if you follow Microsoft Best Practice, you've then broken the lowest permissions Microsoft Best Practices.

 

SIMS .net \ v7 wasn't designed for folks poking the backend. If it was, they would have created reporting views, used row-level security blah blah blah

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...