I have an xpage that on submit of an edit to an existing document, a save conflict is created each time you click the submit button. I am the only one that has access to this application currently so I do know there are not any other users that be be saving also.
I noticed this when I attached a document data source to multiple custom controls that I used in that xpage. When the save document simple action was executed it resulted in save conflicts all the time.
Related
I recently made changes and created two forms in a database residing in a production server. When I sent out the link, the users are getting this error:
Unable to create document, database does not contain design.
I suspect that the database residing in their Workspace is not getting the latest design elements (not in-sync). I tried asking one user to remove the database from her Workspace, sent the link to the database to open it again, and click on another link which I provided to open up the two forms and she was able to access the forms.
May I ask if there's any other way I can do for them to not delete it from their Workspace and re open it again so it will get the latest design elements? Should I request the Notes Administrator to perform some codes in the console?
Form designs are cached by the Notes client, presumably to aid performance. As far as I know, it's not possible to disable the caching.
If users have a database open when you modify or add forms, it's usually necessary for them to close and reopen the database to see the design changes, but they shouldn't ever have to remove the database from the workspace and re-add it. I don't think there's any way to avoid having to reopen the database.
I have seen a problem affecting several users at one customer where Notes wouldn't update its design cache, no matter what they did inside the client. The only solution I found in that case was to close Notes, delete a file named "cache.ndk" from the root of the Notes data directory, then restart Notes. It's been 2 or more years since this last occurred, so it might have been fixed in some version of Notes.
Converting a legacy Notes application to XPages with Extension library.
Using application layout with navigator control for basic site navigation.
Stuck on how to have a navigator menu item open a profile document for editing by administrator type user...
Have an XPage created that binds to the profile form, but not finding way to have it opened on the onClick event of navigator menu item?
Any suggestions?
You can use ordinary data source. First, get UNID of profile document and initialize data source with it.
WARNING: profile documents are cached, you need to restart http or reset application if there is some background change to profile document (otherwise you see old values). Avoid using profile documents with frequent changes!
With XPages, profiles are obsolete. A better approach is to move the contents of the profile to a regular document and then in the application_init () method read all that data into the application scope. If you have updating profiles then this is critical because of the issues updating profiles across multiple servers and JREs.
If you must use the profiles, on the navigator, set it to open the profile.xsp in Edit mode. The profile.xsp then Edits the profile with the Default Formulas of each bound field retrieving the value from the profile using SSJS. The Submit button runs SSJS which iterates through the items on the document and writes them to the profile, but does not save itself to disk.
I am trying to setup xPage as Welcome page for notes client and to be deployed via policies. Only issue it opens up 2 window, one which is Bookmarks.nsf frameset and second one is the xPage. Tried many different ways to close frameset, but some internal setting doesn't like this since its a welcome page frame... any ideas or if somebody has done similar project.
I tried opening a view thru welcome page which opens up the xPage and then to close the view in Postopen event, but no luck. also tried same with Form.
Appreciate help .. badly stuck in it.
One way to do that is:
open your xpage in the client
right click on the tab and create a new bookmark for it
right click on the newly created bookmark and click "set bookmark as home page"
I don't know if you can do that via policies, but at least it works if I do it interactively
You can set this by policy by adding to the ini
StartupDB =
That will load the NSF every time the client opens. This command does not respect the enforce flag as its enforced by default, do not set the enforce flag...
You can also set the nsf to replicate by policy so remote users will be able to open it as well.
I have a document library in SharePoint 2010 that several different teams are using for the same purpose. Each team has their own page that has a filtered view of the document library on it. The document library also has custom columns.
The issue I am running into is when a team member uploads a document from their page. They click "Add document" from their page, and then they browse to the document they want to upload. This part works perfectly - and the URL specifies the source as the team's page. However, after a user selects the document and clicks "OK", it takes them to the EditForm.aspx page that allows the user to fill in the meta data for the document. This is fine, but now the source URL specifies a view from inside of the document library, and no longer points to the team's page (where they came from).
Does anyone know how I can change this source URL to point to the team's page instead of the document library? Or, does anyone know a workaround for this issue so that a user can upload a document from a page (with document library web part on it) so that it returns to the page?
Thanks!!
SharePoint 2010 should work the way you want out-of-the-box. I tried to reproduce your situation, but was unable to. What I did was set up a library with one custom column and two custom views. I then created two pages, one with a list form web part using one view and one with a list form web part with the other view.
When I click on the Add Document from either page, a modal dialog window opens to the Upload page. I first select the file (Upload.aspx) and then am redirected to the metadata properties (EditForm.aspx). After filling out the metadata, the dialog window closes, and the page behind it (the page we were originally on) refreshes to show the new document in the web part. So the user experience is that they stay on the page they want while adding the document as desired.
If you edit your question or provide comments with more details on your situation we can try to reproduce it, but the functionality you describe is exactly how it is supposed to work out-of-the-box.
Peter's correct - SharePoint's being SharePoint.
If I am reading this right, it may be that you should simply check out in-line editing. Using a view, you and edit the properties dynamically without leaving the page (each team getting their own view).
Alternately, I see many who simply want to redirect users back to the page they came from either edit or view of an item regardless of where that was (a link, etc.). Simplest way to do that is a little programming by adding a button to the forms replacing the OK/Cancel with your own code. Simply edit the forms using InfoPath to add the new buttons - you have the user context if you need to custom redirect to a team home page or some such.
We are using sharepoint 2007.
we need to define a process when a user opens a document in a document library.
The process should open a dialog box and take some inputs from the user when user try to open document.
After accepting input and dialog box is submitted then only open the document.
The inputs the user submits must be store in a sharepoint list.
Can that be done using some feature or workflow?
What is the feasible solution for this?
Thanks..