My website users have dashboard containing all the graphs, tables etc. created in excel and now they wish to publish it online.The intranet web server is in LAN connection with client PCs and generally website is accessed something like this:
http:\\10.222.12.52:8080\mywebsite\index.html
Now they are saving the excel sheet with AUTO PUBLISH OPTION ON as a web page (say dashboard.htm) and they wish to view updated dashboard using URL like
http:\\10.222.12.52:8080\mywebsite\dashboard.htm
The problem is while saving excel as web page, we need to enter entire UNC path to website folder i.e. \\10.222.12.52\c$\Apache24\htdocs\mywebsite\dashboard.htm and the same should not be disclosed as almost any user in team (not necessary just admin) would be handed in-charge to save new dashboards quarterly.
Is there anything that can be done as an alternative to UNC path? something like
\\10.222.12.52\mywebsite\dashboard.htm that would be accepted by excel's "save as" dialog box to save the excel as web page..
Related
In our web application, we have direct link to word document in SharePoint site. So when user clicks on the hyperlink, I would like to open that in users local desktop word application. But I am unable to achieve it.
I have tried other work arounds like, when user clicks on the document in the sharepoint site, able to open in word desktop app. But it is still two clicks for user to reach the word desktop app.
Is there any way if we pass any parameters in the url saying open in local desktop app?
Thanks
Below is the code to open the desktop app directly in users machine. It will ask for confirmation though before opening the document in local.
ms-word:ofe|u|https://xxx.sharepoint.com/sites/xxx/xxx/xx.docx
When trying to open excel TFS reports from within Visual Studio we keep getting prompted by excel for security credentials. It says it is trying to connect to
'http://myserver.mydomain.com'.
When I open the project portal using the above domain name in a browser and then try to open the report I get the prompt.
When I use just the server name, in other words,
'http://myserver'
to access the report, the security prompt goes away.
How do I configure TFS (or Visual Studio or whatever) so that when opening excel TFS reports it uses just the server name?
I have definitely run into this one before. It's a safety feature for Excel paired with SharePoint Document Libraries.
Essentially, here are the steps to "trust" the site:
Open Excel
Open Excel Options from the Backstage View
Head to Trust Center on right side at the very bottom.
Click "Trust Center Settings"
Click Trusted Locations
There are several things you want to do here next. If you want to trust network locations then click that option to enable it.
If you want to add a new trusted location then click "Add new location..."
Type in the full URL for the new location and then choose the box for "Subfolders of this location are also trusted."
That should do it!
BTW - from my un, you can have your IT department send these settings to all computers on your Active Directory domain through global policies so others don't have to go through these steps. They can also add this site to the Intranet Sites group in Internet Explorer for everyone internally which should help out in other similar scenarios.
I have a silverlight application inserted in a SharePoint page. The SilverLight application runs on a different server thatn that of SharePoint. From an event in the SilverLight, I generate a document on the server side from SQL Server. I can generate the doc on the server hosting the silverlight application and also copy it to the SharePoint server. I wanted to know if I can include this file in a sharepoint document library automatically. I was thinking if like emailing to a list allows us to copy the file into the library, can we configure the reverse, means copying the file make it part of the list.
Update:
I wanted to avoid uploading. For me uploading is sending the file from one location to the target location. But what I am saying is, if I copy the file into the folder where SharePoint keeps the file physically for the particular list, can it be added to the list automatically?
I am not sure, how well I am being able to describe the point. Please elaborate if required or I can answer your queries.
SharePoint stores the files in a database, not a folder.
WebDAV access may be what you're looking for - it's a backbone of the the Explorer View feature that allows a user to access a document library as if you were accessing a file system through a Windows Explorer window.
You can configure "incoming e-mail" properties for the document library, and assign an e-mail address.
After that, when you e-mail a document as attached to e-mail to this e-mail address, then attachment will be saved to that library by sharepoint automatically.
I have users who want to open Excel attachments from a list item but sharepoint insists that it opens using xlviewer but it never works. There is always an error that says try again in a few minutes.
I just want to allow them to download it or to open it directly with excel or the associated application.
Make sure you're the site collection admin. Go into the site (not the central admin) and then go to site settings then go to site collection features. In there you will find the setting for " Open Documents in Client Applications by Default " it will probably be deactivated. Active it and you're good to go. users will then open attachments in their windows assigned applications, not the sharepoint web apps.
How do you manage deploying InfoPath forms to different sharepoint servers? Is there a better way to deal all the data connections being site-specific without opening the forms, editing the data connections and republishing for each environment?
This is a common problem, if you are working on a dev-system and need deployments to a productive system from time to time. I use a script that performs (plain text) replacements based on regular expressions.
on each deploy:
make a backup of your form ;-)
Save your form as source code. (I suggest you work on source code files rather than the .xsn, because the xsn is only a renamed .cab with the source files in it. And you are able to use source control in a more satisfying way.)
open the manifest.xsf file
search for the xml node "DataConnections"
search and replace the site-url part
(Do not forget the save-path, file-&site attributes and publishUrl)
deploy from the InfoPath Designer
I use a script that does all the replacements. That works fine and already saved me a lot of work.
If I understand your scenario correctly:
You have an InfoPath form, with data connections that submit your data.
You wish to deploy this form on multiple SharePoint Servers and have those data connections submit data to the currently deployed server.
You can't really get around needing to do work on every SharePoint server that you would want to deploy the form to. However, you can get around needing to modify the InfoPath Form Template.
If you use the SharePoint Data Connection Library (DCL), and create a UDC file from your data connection, on every SharePoint Server that you would want to use...then your InfoPath Template can just talk to the UDC file.
Here's a link to an article about integrating InfoPath with SharePoint's DCL:
http://msdn.microsoft.com/en-us/library/bb267335.aspx
If you go into the submit options, there is an option to perform custom action using rules. If you have all of the data connections set up, you can configure rules to select which connection to submit to.
re: speedfox's answer, try to stay away from editing the manifest whenever possible. It'll just lead to head aches.
If I understand your problem, you're deploying to multiple servers (DEV, UAT, Production) and need to edit the data connection manually every time you go from one environment to another? Forgive me if I've over simplified the problem
I've found the best way to make data connections site relative is to:
Use data connection files in your form. Open the data connection wizard in infopath and for all of you data conencting click "Convert..." this changes your data connection from being embedded in the form to being an independant XML file. You'll need a Data Conenction Library on you sharepoint site to store these in. Create that in the browser.
After you've converted and the connection go back into it and there will be a Connection Options... button use it to change from "Local data connection library" to "Centrally managed connection library"
Upload the data connection that is in your sites Data Connection Library to central admin
When you publish your form make sure you're publishing to a centrally managed location (Central Admin)
Use your form as a content type in any forms library on that site collection.
To use the form on another site, upload the data connection file to the new servers central admin and publish the (unchanged) form to the centrally managed forms.
See my blog post where I take you step-by-step with relevant snapshots covering the following:
a. Converting InfoPath Data Connections to DCL library in SharePoint.
b. Publishing InfoPath form to a SharePoint List/Library
c. Creating a .wsp solution package for the InfoPath form and its code-behind
d. Creating a batch script that will deploy the InfoPath form on your Production site.
e. Ensuring the InfoPath form has been deployed as a feature
f. Modify the DCL's in the production environment.
g. Associate the InfoPath Content Type with the Document/Forms Library
See the full blog post at: http://www.sharepointfix.com/2009/12/infopath-2007-form-and-nintex-workflows.html
By site-specific, do you mean that the data connections in your forms refer to the server the form is deployed to? If that's the case perhaps you could tweak your connections to use localhost instead of the server name for the hostname part of the data connection URLs.
In my scenario, I am not using the built-in "save" button. I have a data connection that I use to "post" the data to another list.
Yes, that's what I mean by site-specific. I don't think you can use localhost 'cos then when a user saves the form, it'll try to post to the user's computer (i.e. localhost). I have tried to use relative paths but that doesn't seem to work.