[longlam]

Hi,

We have the ODBC extension provisioned on our account. So far I’ve only given administrators access to the tool. I’m wondering what role attribute I will need to set to allow other users to use the ODBC driver.

-Long
This is a cached copy. Click here to see the original post.

[mhuffman]

The permission is called “Advanced Analytics” under Setup (we will be changing the name to ODBC.) However, there is currently an issue, #112746, where this permission is not showing up if you don’t have the old ‘Enterprise Reporting’ feature on – so if you didn’t have that feature before the new ODBC feature was released, for the moment you won’t be able to give this permission to non-admins. We’ll fix this as soon as possible.

[LogicalApps]

RE: What role attribute to set to enable ODBC access for a user

Is the Advanced Analytics the only permission needed? Or, when you try to connect thru (let’s say) Excel it will look at what other permissions that person’s role has?

For example, I have a custom role called Professional Services that needs access for some custom job reporting. In their role they don’t have access to the Budget, but this is a view that’s available thru ODBC. Will they be able to see it? Can they extract information on it?

Even more important, he’ll need access to the Employee view for some relationships but in that view he’ll be able to see everyone’s SSN amonst other data they shouldn’t.

Any suggestions on a workaround? The only thing we can think of is building our own cube and pulling data down that others can report on.

Thanks for any suggestions.

Erik

[longlam]

RE: What role attribute to set to enable ODBC access for a user

Originally posted by LogicalApps

Is the Advanced Analytics the only permission needed? Or, when you try to connect thru (let’s say) Excel it will look at what other permissions that person’s role has?

For example, I have a custom role called Professional Services that needs access for some custom job reporting. In their role they don’t have access to the Budget, but this is a view that’s available thru ODBC. Will they be able to see it? Can they extract information on it?

Even more important, he’ll need access to the Employee view for some relationships but in that view he’ll be able to see everyone’s SSN amonst other data they shouldn’t.

Any suggestions on a workaround? The only thing we can think of is building our own cube and pulling data down that others can report on.

Thanks for any suggestions.

Erik

This was generally why I believed only Admin’s would have access to the ODBC because having this link will allow complete and total control of all the information in the data file. I think that if you want others to work on only certain pieces of data the best thing to do is to import that information into Access or Filemaker and let them manipulate it from there. This maybe time consuming depending on what tables you are copying over, but this will allow you to control exactly what information is being accessed.

[LogicalApps]

RE: What role attribute to set to enable ODBC access for a user

Thought so. Thanks for confirming our path. We’re testing out some concepts with SQL Server 2005 so we’ll see what that gets us.

Thanks,

Erik

[smudgiebottom]

Hi,

We are on 2007.1 and wanting our Inventory Controller to be able to use ODBC to dump some data into Excel to manipulate.

I have given his role the Advanced Analytics permission, but he cannot see any tables until he has Administrator role as well.

Surely I can avoid giving an end user an Administrator role (which I’m hoping he won’t notice!), just to get an ODBC connection working… Any ideas from anyone on a set of permissions required other than Administrator?

Matt

[Author]

Posts