A new form I just added to a database while troubleshooting has a single editable text field, and a button with #Command([FileSave]) code. That is all, no #DBLookups, no webquerysave agent, nothing but those two things (except computed text showing my common name to ensure I was logged in).
Using a browser (Firefox), the form is presented, and I can edit the text field, but when I click the button I get an error:
Error 404
HTTP Web Server: IBM Notes Exception - Entry not found in index
this is the error shown in the log:
HTTP Web Server: IBM Notes Exception - Entry not found in index [/dev/testcore.nsf/mgs?OpenForm&Seq=1] CN=Matthew Smith/O=mydomain
We have restarted the server completely (if that helps), but still getting this error. I do not understand how this could be happening. Existing forms in this mature database save fine, but not this one new one.
There's very little to go on here, but I suspect that your database either has no views or has no default view. One of the things that happens when you open a document (as opposed to a form) is that it needs to determine if there's a Form Formula that applies to that document. If there is no current view node in the URL, or if the view node is '/0/', it should look for the default view to check if there's a Form Formula defined for the view. If there's no view at all, or no default, I can see that generating an "Entry not found in index" error since no default view entry is found in the index of the design notes collection.
Related
I am a new user to LiveCycle (LiveCycle ES4 to be exact) and am having an issue with my second Master Page. I only want the second Mast Page to appear if the content from Page 1 overflows onto Page 2. I have tried changing the "Presence" on the second MasterPage to Hidden but the program won't allow me to choose any option other than Visible.
I have tried Google and Adobe and both have basic information regarding Master Pages but nothing specific enough to help me in this situation. Actually, I haven't been able to find a source with any real helpful information regarding LiveCycle.
On the main page that represents your flowed page, in the Object properties tab, if you select the Pagination tab, you can set overflow properties of this page to use your second master page (ensure it is named so you can reference it). If your first page never overflows, then you should never see the other master page.
I have an URL that points to a Lotus Domino database, for example:
http://domino853.example.com/db.nsf/wcms/BEC4D26AD7A56823C1257B4B003427A8?OpenDocument
How is that URL mapped to the Domino form?
My first thought was the UNID is looked up in the database, and that the rest depends on the Form item of that document. But that's not the case. The actual form that gets resolved is neither wcms (like in the URL), nor document (like in document.Form), but it is wcms_createdoc. So where could that come from?
After some research, I found it:
wcms is an alias for another view.
That view has #Text(#DocumentUniqueID) as its first sorted column.
And, to select the proper form, it has a Form Formula set.
So this is how it all happens:
The view wcms is resolved. Since the URL continues after the view name, the rest of the URL is the key into that view.
The first document of the view that matches the key is selected. Obviously, for the DocumentUniqueID there can be only one document.
Since the view has the Form Formula set, it is evaluated and maps to the form wcms_createdoc.
This form is rendered.
References:
http://www.ibm.com/developerworks/lotus/library/ls-Domino_URL_cheat_sheet/
I am programming the On_Click method for the button labeled "View" in the first printscreen below. The method will load a form with data corresponding with the specific address id in the row containing the "View" button. This code worked perfectly when pointing to a target form called "Addresses". However, when I decided to rename the form "Address", I started receiving the following error message when clicking on the view button:
I did some research on the web about this error message, which lead me to try to delete any outdated references in the VBA editor. But when I clicked on Tools-->References in the VBA editor, I got the following error message:
It seems that MS Access' entries in the system registry might have been corrupted. But I am not certain of this because the documentation of this on the web is sparse and inconsistent.
Here is a link to the database on a file sharing site: http://jmp.sh/b/9Uyx6J2YzWbs8zPq2h6g
If the problem is in the database, you can recreate the problem by opening the form "Main" and clicking on the button "View" for the record shown in the printscreen above, or for other records.
Can anyone show me how to get past this error message?
my advices?
You could rename your Forms!....SourceObject to "Address" instead of "Addresses"
You could copy/paste the form, delete the original, and retry
You could install a decent debugging tool like MZ-Tools for VBA, that will help you manage your errors. Check the details here
EDIT: I used to get similar bugs years ago, when I was writing specific form event procedures. As we decided to switch to a model where forms did not need to be debbuged anymore (check this here), we stopped getting this kind of message. And I think I forgot the trick we used to solve this kind of error. If I were you:
I'd try to open another access database and import all objects ...
I'd put aside/cancel the faulty onClick procedure
And I'd install MZ Tools because otherwise VBA debugging is a nightmare ...
Since access was not liking the command button in each record of the continuous form, I choose to put the view button's logic in the on click event of a text box in each row, which I configured as enabled but locked. This produces a separate link from each record of the continuous form to a unique detail page with more of the chosen record's data.
This solution works perfectly, and is enabling me to move on with my other coding.
However, it would be nice if someone else were able to show how to get the command button solution to work.
I am implementing a series of rdlc reports on a webpage using a ReportViewer. When the report is initially generated is works fine but when I try to change the page of the report the following error is displayed:
"One or more data sources is missing credentials"
I have checked that the Data Source of the Local report is set correctly and the fact that the first page of the report is correctly displayed is proof of this.
When I export the report to a PDF or any other format it correctly includes all the report pages.
I have also tried implementing the PageNavigation event but this error is thrown before the event is called.
Does any one have any incite into this issue and what solution there may be?
Ok I found the the problem. I had a setting AsyncRendering set to false in order enable the reportviewer to stretch to the full width of the page.
Unfortunately this causes a postback and the enitre page is reloaded and obviously the datasource is lost.
Unfortunate as I will now have to manage the width of the reportviewer manually and it does not look great.
Anyway solution is to ensure AsyncRendering = true.
In one of my custom application user wants to keep EditForm.aspx open once list item is created and he can keep saving the same record without redirecting user to DisplayForm.aspx page.So what I'm doing after list item creation I'm loading EditForm.aspx again.
Now the problem is when form is opened in Edit mode and if existing field is modified that doesn't gets updated in the list item but if something new added to the field then it gets saved to the list. I believe it's postback issue but not sure how to pass latest form data upon save.
If this was my task, I would create a new application page that replaces the edit page on that list.
(You can use powershell / object model to set the url of the new / edit / display pages)
Ignoring the ribbon, the edit page is actually pretty simple. It shouldn't be too difficult to create a custom one, that has the submittal behavior you are interested in. Indeed, since you are keeping the exact same field names and input types, you may be able to simply inherit the default form in yours, and simply override the post call.
I suppose it might be possible instead for you to write some javascript to hijack the submit post of the default edit page, but this seems messy to me, and I probably wouldn't go that route.
If you don't need to complete this task today, I've been meaning to push to github some code I wrote a few months ago. That code is a custom aspx edit/new/display page that is extremely easy to customize / implement. I could forward you the link tonight when I get out of work.