Suppose i have a dashboard in my local system, and the same dashboard as web service, can we see the live changes in web dashboard if we apply some filter in the local version.
Is there such option?
If you are working off a truly local copy of the workbook, then any changes you make to that workbook will not be reflected in the server based version. Similar to working on a Office file with another copy on SharePoint, changes you make local do not sync to different physical copies of the file.
A couple possible solutions
You can use the web-based edit functionality of Tableau Server to make changes to a server-hosted version that are seen by all users
Any edits to the data source are "seen" by Tableau at the time of the data query, so any filtering you apply to the data source will get picked up any time the Tableau desktop/server engine queries the data source. This also applies to any saved data sources you are publishing on Tableau Server (which can be used by workbooks both on Tableau Server and Tableau Desktop). Note that if you are using TWBX files, those are by design self-contained and won't pick up upstream data changes without a manual refresh.
Related
We have 5 tables inside a database and we want to sync the data inside those tables to SharePoint online lists. All the modifications will still happen on the database tables, so the sync should only sync New/edited/Deleted data from the database to SharePoint and not from the other side.
The database tables can be accessed using ODBC. So what are the approaches we have to do such a sync:-
Using Power Automate Flow which runs on schedule basis?
Write a .net console application which reads the data from the database and update SharePoint using CSOM?
Other approaches
Any advice?
Thanks
I've been working on a PowerAutomate sync between an Excel Table and a bundle of Sharepoint lists, and one component that is proving quite useful for the Excel -> Sharepoint update direction is the "Sharepoint File or Folder Created or Modified" trigger.
If your database platform has the capacity to create small csv or json files corresponding to the changes you want to make, then one option might be to set aside some "new, change, delete" folders accessible to your PowerAutomate profile and to have your system pass in files with the records to be changed. Particularly if your db tables are particularly large, this might be a more efficient solution than periodically scouring the whole table to try to identify those changes proactively.
I have a data file that has two Microsoft Query Connection Queries that pull data from an outside source. My goal is for these connections to update automatically within my local Microsoft Excel application. I have uploaded this Excel file on to the online version of Microsoft Excel, thus when it updates automatically in my local Microsoft Excel version, it will update the online version.
This refresh needs to be done independent of use of the system, meaning that no person will need to open the file or refresh the file, the local Excel version needs to not be opened by a person, but could be by some sort of code.
I have tried using the automatic refresh after [x] minutes, but that will only update when I open my local version AND that amount of time has passed. I do not want to have to open the local data source, because the eventual goal is to have a separate system that will update this in the background, that I do not manage at all.
If you have any advice on how to make this work, that would be great!
We are trying to create a demo version workbook which will have predefined data persisted in it. But this functionality is not available for public users we have a dev mode manifest with similar id to that of the submitted manifest. If we persist data using this dev mode manifest we couldn't access it from the Add-in available in App Source. Could anyone let me know why we couldn't access this data and is there a possibility to resolve this ?
I think you can go two ways:
Excel way: Create and use one sheet (can be hidden for user) as a data table for app, in this case when you are starting your app you just need to check the sheet existence by its unique name. This case acceptable for any workbook movements and user will not lose its persistent data.
Web way: as Addin itself is a WebView you can use LocalStorage as same as IndexedDB, which brings all power of local database for your app. In this case the data will be tied with exact PC and user will lose their data if you. But again, as it is web technology you can synchronize it with any remote Database to keep track of any changes.
I want to link an excel file to SQL Server 2014 whereby I can edit the file and the data gets updated on the server automatically.
Similar to what happens when you link sql server to Access whereas you can edit the data and the changes take effect in the server.
Thanks in advance
There is no out of the box solution for this. You can do this either of two ways:
Write a C# code which has a file watcher attached to the Excel file which uploads the Excel file using SSIS job to the database.
Create a scheduled SSIS job which imports the Excel file periodically.
Understanding the purpose would allow for greater elaboration.
This depends on the type of data you wish to edit.
For master data, if you have the Enterprise or Business Intelligence edition of SQL Server and Master Data Services set up, there is a plug-in for Excel:
https://msdn.microsoft.com/en-us/library/hh231024(v=sql.120).aspx
For transactional data, I would strongly advise against using Excel as a front-end and would recommend you to consider alternatives.
However, if you are compelled to go down this route, you can achieve this using VBA scripting and linking via a DAL (Data Access Layer) such as ADO.NET. Be aware that giving such power to your users could open up your system to sql injection attacks - only proceed so if you trust the users 100%. Another thing to take into consideration is validation checks - validation checks should be applied to every cell where data can be entered. More information can be found here:
https://support.microsoft.com/en-us/kb/316934
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).