Hi all,

Quick level-setting - I'm not a SF Developer, I'm an Ops Analyst who's strong with data.  Knowing this, I'll pose my question below and ask that you give me some patience if I don't fully understand a response.

I'm using Excel 365 to 'Get Data from Salesforce Objects'.  This feature is now baked-into Excel (used to be called Power Query), and uses it's own query language called 'M'.

I've written the query to extract only the info we need from the relevant objects.  The query handles the call, all calculations, and inserts the data into a table in Excel.  I have all my pivot tables set up from that table of data.  Functions flawlessly, seamless experience, etc.

Intent is to distribute this tool to multiple management users and train them.  When a user refreshes for the first time and the query runs, Salesforce recognizes the new PC/user and asks for their Salesforce username and password...etc.  We now have this in the hands of about 20 managers.

Here are some of my questions:

1. Does this query hit the 'SF API'?
2. How is this handled by the SF application, specifically, is it more/less taxing than running a report from the reports tab within SF?
3. I see an API call limits page here in the developers site - do these API limits apply to this type of query? 
   • If so, can you help me gain a better understanding of our limits?

The reason for this post is as follows:

Our Salesforce team was aware of connectors like this, but not Excels ability to do so.  Now that I have brought it to their attention, they have some concerns, and are making the suggestion that they create a single Username and Password which we would all use.  They would control the role and permissions associated with the single username so as to limit it to only our needs, effectively addressing some of their concerns.

The long-term goal would be for this tool to be used by 170+ people, each refreshing the data as they see fit, but I would expect each would only refresh once in the morning, once around lunch, and once before the end of the business day.

Would a single Username being used by that many people experience issues?  API call limits?  etc?

Please share any thoughts you have on this subject, including anything I should be considering.

*Right now we're exploring this solution.  We recognize we could explore other solutions like a single extract every 5-10 minutes which we could then point users to.  For now, consider this off the table.

I appreciate any responses and look forward to the discussion.

JR
 

Hi all,

Quick level-setting - I'm not a SF Developer, I'm an Ops Analyst who's strong with data.  Knowing this, I'll pose my question below and ask that you give me some patience if I don't fully understand a response.

I'm using Excel 365 to 'Get Data from Salesforce Objects'.  This feature is now baked-into Excel (used to be called Power Query), and uses it's own query language called 'M'.

I've written the query to extract only the info we need from the relevant objects.  The query handles the call, all calculations, and inserts the data into a table in Excel.  I have all my pivot tables set up from that table of data.  Functions flawlessly, seamless experience, etc.

Intent is to distribute this tool to multiple management users and train them.  When a user refreshes for the first time and the query runs, Salesforce recognizes the new PC/user and asks for their Salesforce username and password...etc.  We now have this in the hands of about 20 managers.

Here are some of my questions:

1. Does this query hit the 'SF API'?
2. How is this handled by the SF application, specifically, is it more/less taxing than running a report from the reports tab within SF?
3. I see an API call limits page here in the developers site - do these API limits apply to this type of query? 
   • If so, can you help me gain a better understanding of our limits?

The reason for this post is as follows:

Our Salesforce team was aware of connectors like this, but not Excels ability to do so.  Now that I have brought it to their attention, they have some concerns, and are making the suggestion that they create a single Username and Password which we would all use.  They would control the role and permissions associated with the single username so as to limit it to only our needs, effectively addressing some of their concerns.

The long-term goal would be for this tool to be used by 170+ people, each refreshing the data as they see fit, but I would expect each would only refresh once in the morning, once around lunch, and once before the end of the business day.

Would a single Username being used by that many people experience issues?  API call limits?  etc?

Please share any thoughts you have on this subject, including anything I should be considering.

*Right now we're exploring this solution.  We recognize we could explore other solutions like a single extract every 5-10 minutes which we could then point users to.  For now, consider this off the table.

I appreciate any responses and look forward to the discussion.

JR
 

I am trying to connect Microsoft Access (from Office 365) to salesforce.  I have followed the instructions in the following link:
https://support.office.com/en-us/article/link-to-or-import-data-from-salesforce-7375ffb6-1d6a-46f1-bb0c-c6ac3c58f5a0

When I attempt to link a new table to Salesforce, I use my credentials in the Connect to Salesforce login.  Then I get a linked tables dialog, in which all the Salesforce objects are listed.  I choose one, then get the following error:

The Microsoft Access database engine could not find the object MyOrg..Pricebook2.  Make sure the object exists and that you spell its name and the path name correctly.  If MyOrg..Pricebook2 is not a local object, check your network connection or contact the server administrator

I have enabled the Use Any API Client permission for myself.  However, in the Connected App persmissions, I haven't been able to find anything I can identify as what Microsoft Access is using.  This might be a clue.

Thanks for anyone's help!