I'm trying to do a 2-way sync with an excel spreadsheet and a list on my sharepoint 2013 online public site. Research has told me that the best approach, without using 3rd party solutions, would be to use Access 2013, and to first sync the excel spreadsheet to the access database (I've done this). Next would be to sync the Access database with a sharepoint list. When I try to do this, it publishes the table as a list, but if any changes are made to the excel spreadsheet, it's not updated on the sharepoint list. Is there a specific way this needs to be done? I wasn't able to find any good documentation on this, especially for 2013 versions.
Thanks for any help!
Related
I have a PowerBI Online dataset, which was created in PowerBI desktop and then published online. So far so good.
I connect to the dataset from Excel via PowerBI pusblish, which work as expected. I'm able to refresh the data in the offline version of Excel, but if I attempt to refresh it in Excel online, I get a generic error.
Is it even possible to refresh Excel online which is connected to PowerBI dataset? If not, any possible workaround?
Thanks for any tip
I'm not sure if this is an exact answer, but I've got a set up here where the O365 online excel document lives in a sharepoint environment. I was able to add the sharepoint site as a source in PowerBI - so whenever the online excel gets updated (because it resides on the sharepoint server), it's able to be fed into Sharepoint.
Does anyone knows a way to publish my PivotTables and PivotCharts made in Excel, Access, or PowerPivot 2010 to a web page and maintain the interactivity?
I know this was possible in Excel 2003, but cant find a way to do the same in Excel 2010 without having to use Sharepoint and Excel Services.
Any suggestion?
Thanks
In terms of PowerPivot based files this isn't possible.
Jacob
The cheapest and easiest option would be to put the dataset in Azure or Azure Marketplace and have them query the data directly via the PowerPivot plugin. Other than that you can not maintain the interactivity of the pivot chart online. It's not part of your question but I would suggest taking a look at a http://www.highcharts.com/ or http://d3js.org/ implementation. You can interact with an example here:
http://www.highcharts.com/demo/pie-basic (click jsfidle)
If you get to the point where you can justify the cost of having powerful reports online you can take a look at http://spotfire.tibco.com/demos at our last company we had so many requests for pivot tables and their charts to be accessible online that we ended up having to buy a Spotfire license :/
Good luck!
I use Office 365 plan E3 and I want to copy and modify an excel file within a document library on the server. Goal is to read some values from a listitem and update the excel with these values. In the excel file there are several formulas that do the reporting the customer wants.
I already tried developing a sandboxed solution with excelservices.dll referenced, but SharePoint doesn't allow to execute this solution because of partial trust problems.
I also tried to generate a proxy for ExcelServices.asmx, but WCF needs a configuration file and in O365 I can't change web.config to add the config-sections - and it's not so much fun to generate and parse soap messages manually.
Are there any suggestions how to solve this or is it still impossible?
SharePoint have some embedded function of Excel services - maybe You can use webpart like Excel lists or something similar?
I have a SharePoint 2010 site with a document library for storing Excel files. If someone is editing an Excel file (using stand-alone Excel, not Excel services), everyone else will be forced to open the file read-only until the first person is done editing. Is there a way around this? What I want is to allow two or more people to be able to edit the file at the same time. Also, I don't want people to overwrite each other. Instead, I'd like SharePoint to merge their changes. Is this possible in SharePoint 2010?
No, sadly:
The Excel 2010 client application does not support co-authoring workbooks in SharePoint Server 2010. However, the Excel client application does support non-real-time co-authoring workbooks stored locally or on network (UNC) paths by using the Shared Workbook feature. Co-authoring workbooks in SharePoint is supported by using the Microsoft Excel Web App, included with Office Web Apps
From Co-authoring overview (SharePoint Server 2010)
...and not for SharePoint 2013 either. Though it works for pretty much all other Office documents. Go figure.
The new version of SharePoint and Office (SharePoint 2010 and Office 2010) respectively are supposed to allow for this. This also includes the web based versions. I have seen Word and Excel in action do this, not sure about other client applications.
I am not sure about the specific implementation features you are asking about in terms of security though. Sorry.,=
Here is a discussion
http://blogs.msdn.com/b/sharepoint/archive/2009/10/19/sharepoint-2010.aspx
Yes you can. I've used it with Word and PowerPoint.
You will need Office 2010 client apps and SharePoint 2010 foundation at least.
You must also allow editing without checking out on the document library.
It's quite cool, you can mark regions as 'locked' so no-one can change them and you can see what other people have changed every time you save your changes to the server. You also get to see who's working on the document from the Office app. The merging happens on SharePoint 2010.
Unfortunately, the file must be locked for updates unless you're using Office 2010 and SharePoint 2010 together. This means that only one user per time can edit a file. The locking and version tracking capabilities of SharePoint are excellent, and this makes it a great tool for the type of collaboration you're talking about, but you would have to split documents into multiple files in order to extend the amount that could be edited at a time. For instance, we sometimes unmerge documents into technical, requirements, and financials sections so that the 3 experts required for the review can work concurrently. We then merge when everyone is finished.
yes if it is SharePoint 2010 and above by using the Office feature co-authoring
Just curious what the experience has been in uploading MS Access tables to SharePoint 2007 list. We've been planning on doing so, but I seem to recall issues with SharePoint mangling Access tables in the resulting lists and generally the migrations not going so well. Your experiences? Best practices and recommendations? I'm particularly concerned on its ability to migrate forms and reports as well if it can do so. Thanks!
In response to a question from UK SharePoint User Group I wrote a blog post on Using Access 2007 with SharePoint lists which you might find interesting (some interesting comments too).
There is no facility to migrate forms or reports in Access 2007/SharePoint 2007, only tables. Lots of new stuff in Access 2010/SharePoint 2010 which will allow you to create Access Web databases for SharePoint.
Derek
As mentioned, the big news for Access 2010 is we can build web sites and publish applications to the web. Here is a video of me running ms-access in a browser (the 1st part is in the client, but you clearly see me switch to the browser version of the application about ½ into the video):
www.members.shaw.ca/MrTurtle/2010d1/w1.html
For access 2010 the tables (or so called lists) are going to have things like cascade deletes, cascade delete restrict. There also again a whole bunch of performance improvements that will allow much larger list sizes to perform well.
Note that the new table triggers (data macros) will also go up to SharePoint when you publish the database.
For access 2007, there is not really any particular special problems, but there is just more limitations compared to the next version of access that is coming out. So for example if you need to link up a whole bunch of related tables you have in 2007, when you push the tables up to sharepoint, you don’t have any cascade deletes or any RI options like you’ll have in access 2010.
So I don’t recommend pushing up an application with a whole bunch of interrelated tables. It just not going to work. However, if you have a simple customer list or contact list of a few thousand names that you need to share, then access 2007 should work just fine for you.
So, keep in mind if you have a list or table you need to share, then fine. However, you not going to have any luck or success if you have a whole bunch of tables that are interrelated, and you need to run the application in that fashion.