One of my customers is very impressed with the capabilities of PowerPivot, particularly the analysis capabilities but even more the publishing capabilities. With that I mean the ability to publish a dashboard to a SharePoint site, after which it can be experienced directly in the browser, including filtering and slicing for end-users.
As we publish our PowerPivot results to a SharePoint site, we get the following error for any action that triggers the data connection to refresh:
The data connection uses Windows Authentication and user credentials
could not be delegated
I've done a lot of research on this one and it seems it is a configuration issue on the SharePoint side. Note though that we are using a cloud hosted SharePoint thus the environment is not under our control. In addition, even our own team mentions this to be a security restriction that will not be lifted.
Therefore, I'm not working on solving the above problem, rather on avoiding it alltogether:
My first experiment was to build a "normal" Excel file without PowerPivot. Same data and I managed to build the same pivots. Both the data and the pivots are in the same file, without a data connection. Publishing it works just fine. The error is not experienced this time, and even interacting with the report via slicers works.
As a second experiment, I wanted to follow the same scenario, but this time using PowerPivot. From data in an Excel sheet I created a so-called "linked table" in PowerPivot. Next, I created some pivots that make use of this table. The pivots are in the same Excel file as the original data. When I publish this file to SharePoint, I get the same error mentioned before when doing anything that refreshed the data connection. Even though the data and pivots are in the same file, it still pops up with this security error, which surprises me.
How can I work around this data connection issue when a PowerPivot is published? We'd like to have both the analytical power of PowerPivot as well as having the rich publishing options of Excel, without running into the data connectivity issue. Is it possible to "flatten" a PowerPivot file to "normal" Excel, since experiment #1 shows that this works fine. How can I remove the data connection from PowerPivot and tell it to just use the Excel data in the very same file?
Do you have PowerPivot for Sharepoint installed?
Is it Pivotstream providing the cloud service?
Related
There does not seem to be a way to set up automatic refreshing of data from Sharepoint like there is with a SQL server.
The main difference from what I can tell is that Sharepoint is only listed as a Data Table, with no Data Connection Settings.
Data Connection
Data Table
How can I can I set up Spotfire to automatically update the data from Sharepoint once a day? I've tried various JS and IronPython scripts, although not specifically designed for Sharepoint data updates and I've had no luck so far.
I had contacted Spotfire support and at the moment is it not possible to do automatic updating from Sharepoint. They may or may not add it in the future.
I just recently realise, while using Excel, it lacks on features for being able to update SQL server data through their worksheet.
I have tried using Data-->From other sources--> SQL Server data; that works like a charm but as it has limited ability (View and only get the latest data but not update).
I don’t know if this is done purposely by Microsoft as a money making schemes.
But through my research today, I also came across PowerQuery, and It seems to do pretty much what Data add-in did escape it has few new extra features and sounds pretty advance, therefore, I was wondering if this add-in has the ability to update SQL server data using excel sheet, if so can you guys advise me to the right direction:
I came across lots of commercials products that did the job but frankly speaking, I cannot afford it.
The best solution for in this space that I've seen is the Master Data Services component included in SQL Server (Business Intelligence or Enterprise Edition). This includes an nice Excel Add-In for maintaining data, a Web UI and SQL Views and Staging Tables for data integration.
It doesn't have any direct integration with Power Query, but I would let PQ dump data into Excel Tables, then copy and paste the data into Excel tables using the MDS Add-In.
I need to give power-users of the web application I am working on the ability to create their own reports, analysis, etc. in Excel. Basically they need to create some Excel sheets, read some data from the web app and than mix the result with further data coming from other data sources.
The web application already exposes data in JSON/XML format through a web api (not fully REST but this doens't matter) and I would use this channel to get data in Excel.
At the moment I have these three options in my mind:
In the past I've solved a request like this with some VBA code and a COM object (that talked with the server/database) but I am not sure if today this is still the best solution to do this kind of job.
I have learned that today Excel has PowerPivot that can read data from a web service. I could develop an oData feed for PowerPivot but I am not sure if PowerPivot is what power-users need
Another solution could bean ad-hoc Excel add-in
How would you solve a request like this?
Power Query would be a better option than Power Pivot here. Power Pivot is a dimensional modeling and analytical database (it is exactly a private instance of SSAS Tabular running behind the Excel process).
Power Query is an end-user friendly ETL tool, developed as an add-in for Excel, and available natively as of Office 2016. It allows loading directly to an Excel worksheet or into a Power Pivot model. It will give more flexibility to your end users. It is a GUI-driven interface that is a front-end to the M query language, developed by Microsoft.
Unfortunately, I am not able to help with Power Query too much, but it fits your use case perfectly.
Edit: An additional feature of Power Query, likely not to meet your needs, but I thought I'd throw in.
Power Query can read directly from HTML tables. If you present data in HTML tables, your end users can simply load directly from a URL.
Power Query definitely the "correct" tool for this within Microsoft world. It can also handle JSON and XML (and Odata) directly. How well it manages your data will depend a bit on how nicely formatted it is, but it can work with most things with a little bit of effort.
It is a free Microsoft authored add-in for pre Excel 2016 and built in to Excel 2016.
I'm hoping this is possible.
The organization I work for has a Sharepoint site and I am able to Upload Files to pages, however I am not an admin on our Sharepoint. I'm not sure what the version is, I think its older (ie: 2005).
I have some Excel Reports I've built. The data for these reports is pulled from a SQL Server Database which I have full control over. I have setup a Job in SQL Server to run every 12 minutes, this procedure pulls in some data and updates a few tables. These tables are used to feed my Excel Reports.
I have a separate Scheduled task set to open my excel report(s) refresh the data connections and save as a PDF.
I would like to link to these PDF Files via our Sharepoint so that the VIPs can access the reports as they want, but they always see the most up to date report.
I was trying to link to a Shortcut to the PDF Files but SharePoint doesn't seem to like that. How do I make the SharePoint link point to the PDF File that is saved over every 15 minutes?
Thanks in advance,
Any insight is greatly appreciated.
The way I do it (newish version of Sharepoint) is make the save location for the PDF the network location where Sharepoint keeps the files for that site. Usually you'll have access to those if you can edit the Sharepoint site.
Here is a tutorial to find that network location.
EDIT: It very well may be disabled by the admin at the moment. But it looks like the functionality is there.
Given the age of your SharePoint (either 03 or 07), most of the modern tools that you could use to do this don't exist for you (Excel reporting, BI tools, etc). The easiest solution I can think of is to actually modify the other side of the equation. A few options:
Change your report to output two copies of the same file. One entitled (as an example) currentreport.xls and the other report20150626.xls . Put the link to the currentreport.xls in SharePoint.
Build an ASP.net page that runs the SQL query you have built and pull the data through a view. Since this would be pulled on demand, it may be a few more cycles of your SQL code, but indexing, caching and selective data pull can prevent this from being an issue. Put the asp.net code in an iFrame in a SharePoint content editor web part.
Build your report using SSRS and host the output of that in SharePoint using an iFrame.
Run a scheduled job in SQL that copies your current report data to a table and query that table instead of your normal report table. That way you only have one Excel file that points to a specific table so no need to update links. You can always keep copying data to specific files if you need a historical record and can't use the DB to store this data for you (though the amount of space that it would take to do so would be minimal).
I'm trying to implement an Excel Services reporting solution in SharePoint (MOSS). Since the source data is a SharePoint list, this problem is doubly frustrating. I keep bumping up against permissions problems, even though I've enabled virtually everything in sight.
The first error is about refreshing external data - it's not (really) external data, but that's a semantic point.
The second error is a cryptic "Excel Web Access" problem.
Anyone get this to work??
Could be a couple different problems. The first possibility is that Excel Services doesn't support using SharePoint list data (crazy I know)... although this only applies if you try using the type of embedded data source you get if you choose Export to Excel from a list (again, I know crazy).
However an easy way around this problem is to use the SP webservices to get you list data. I had a macro written by someone at MS a while back that automated this conversion, if I canfind a link I'll post it. If you are using Kerberos then you task is probably finished. If using NTLM then you may need to also configure an SSO application so that the right credentials can be passed to the webservice (or any other data source for that matter). There's a pretty good step by step here.
One kind of "hack" to get this to work via UDF's (which if trusted, custom code can be deployed and made available via Excel Services) can be found here.