Lotus Notes XPinC DateTime format issue - xpages

I am working on a XPage application which will work on both web and client. There is an action which will adjust the date object to 20 days and store it again in the current document. I got an issue, that the code is working perfectly on web and win-xp OS XPinC. I found that there is an issue with win-7 XPinC. And compare with two different win7 machine for the same document. But working on PC but not in another. Finally concluded with that the issues is due to the current machines datetime settings. But I cannot go and check/change all the pc's datetime format. Please advice how can I handle this.
Thanks in advance.

This has been doing my head in for several days.
Xpages works great in my browser, but the date/time is all screwed up when viewed in LN.
The solution is to go into "File" -> "Preferences" and then "Regional Settings".
Change "Content Language" from "English" to "English (United Kingdom)".
A pet hate of mine is that most computers default to the crazy US way of displaying the date, i.e. month/day/year when the rest of the world uses day/month/year.

Related

Xpages : Time Picker, Cannot type specific time (Domino 9 Server)

I need help regarding time picker in Domino 9.
I cannot type an specific time in the textfield. but when I try to put my application in domino 8.5, it works fine.
Time picker only allows time with every 15 mins. and I cannot modify it using the its textfield.
My output should be like this. (12:13 AM)
I there any solution regarding this issue?
regards,
Thanks!
[Edited]
I suggest you to check your version and install the FP2, since this FP corrects a bug related to the default value of the pick date. I'm sorry I can't test the Xpage now.
[original response]
In The standard client it works (I can edit the field), maybe should you install FP2 see http://www-10.lotus.com/ldd%5Cfixlist.nsf/WhatsNew/7ff6a78cb16153d085257d2b0062d7b8?OpenDocument. Which mentions:
+HOKA8RZ5KL (LO67745) - Fixes issue in Xpages where the
correct date (or time) won't show on date time picker. This is a
regression in 8.5.3.
I tested with IBM Notes 9
Social Edition
Release 9.0.1FP2 SHF202
Revision 20140804.1000-T00202SHF-FP2 (Release 9.0.1FP2 SHF202)

Error 5337 submitting InfoPath form to SharePoint

I have some InfoPath 2010 forms with custom code that submits information to SharePoint 2010 form-enabled libraries. One of the forms has a date field, chosen by a picker and stored in a Date/Time column in the library. The form had been working fine for months, but one day it just started failing with the following error:
There has been an error while processing the form.
Click OK to resume filling out the form. You may want to check
your form data for errors.
When I click "show error details", it shows error code 5337 and gives a correlation ID.
When I look up the error in the event log, the details are as follows:
Business logic failed due to an exception. (User: XXX\frank, Form
Name: Miscellaneous Form, IP: , Request:
http://intranet//apps/_layouts/FormServer.aspx
XsnLocation=/FormServerTemplates/Miscellaneous
Form.xsn&Source=/apps/SitePages/expenses.aspx&DefaultItemOpen=1,
Form ID: urn:schemas-microsoft-com:office:infopath:
Miscellaneous-Form:-myXSD-2012-05-14T12-19-23,
Type: FormatException,
Exception Message: String was not recognized as a valid DateTime.)
I am at a complete loss to understand how this problem can have arisen. No aspect of the solution was touched between when it was working and when it stopped. The date format on the InfoPath form is the same as the date format in the SharePoint list column. The system locale and regional settings are consistent everywhere and have not been changed. The problem arose after a slew of Windows updates on the 20th of January, so I'm wondering if one of those might have caused the problem.
The next steps I plan to take are to rebuild and redeploy the form to see if that fixes the problems. However this is code I inherited and it's part of a larger solution, so I'm nervous about redeployment in case I break other things. That's why I wanted to ask here if anyone has come across this or a similar problem before and can to point out something obvious that I might have overlooked.
Thanks for taking the trouble to read this. Any advice would be very much appreciated.
I've faced some issues with InfoPath after Windows and/or SharePoint updates, so you should not rule out that as root cause of the problem. I would check for any known issues using the updates's name.
Regarding the DateTime format, is your custom code setting the DateTime value? If the answer is yes, make sure you are using the following format for the date.
infoPathField.SetValue(dateFieldItem.ToString("yyyy-MM-dd"));
One other thing, can you check the SharePoint LOGS and copy the exception stacktrace?

View. Show values as Links. Strange behaviour

Xpage (listPostits.xsp) has a "View" container control, where one of the column is set "show values in this column as links".
Now, here comes "Strange behaviour".
When i work with this application on my own (developer) PC (Win XP, Chrome or IE), the Domino generate the link, which can't be really processed:
/servername/db/postit/postit.nsf/listPostits.xsp/onePostit.xsp?documentId=many_numbers&action=editDocument
Namely, the Bold-marked portion shouldn't be there ! This portion is the name of the XPage, where the View control is in.
When i work with the application from other PC (Mac, Firefox) then i get the correct link (the same as above but without the XPage name inbetween):
/servername/db/postit/postit.nsf/onePostit.xsp?documentId=many_numbers&action=editDocument
update: let us leave for the moment the differencies in generated links between two machines. The first question is - why the extra portion is inserted into automatically generated link?
After playing around i think i might have found the reason for this strange behaviour. Namely, the "Substitution" Rules on the server side. One of them is to substitute "*/postit/all" with "/db/postit/postit.nsf/listPostits.xsp"
If i switch it off, then the Links are generated properly. Still, it's pretty strange to me that these settings influence the way Domino generates the links. I thought it works on the fly with them and those settings have nothing to do with the way how Links are generated inside the application.
So, the help now is needed regarding Web Site Rule Topic, but for that, i guess, i have to create another topic. But in case somebody has some good Info on this, please share it with me. I'm a bit confused at the moment :)
Final Update: Spent some more hours of testing and the results confirmed the initial idea.
If i open the page with the standart URL, i.e.
http://servername/db/postit/postit.nsf/listPostits.xsp then everything is fine, links are generated properly. When i however open the same page with short URL http://servername/postit/all , then server adds the substitute URL (db/postit/postit.nsf/listPostits.xsp) to every single link he generates automatically to be used as the link to open/edit the underlying document.
Is it bug or feature ? Don't know.
As a workaround (because i want to keep simple URL's for the application) i have to manually generate links.

CodeIgniter calendar date display - showing one day early in production

I'm using the CodeIgniter calendar class to generate an availability calendar. I use a loop to check if a date is in the "reserved" array, and if it is, give that cell a class of booked.
For some reason, on my server (Ubuntu 11.04), when the calendar is displayed the booked dates are showing one day earlier than they should. I'm trying to debug this, as the problem does not appear on my local machine and the values in the database are correct. Since it works on my local machine, I think it shouldn't be a code problem, either.
I've verified that the php.ini settings for date.timezone are identical, and the system dates (when you type 'date' in command line) are also identical.
Can anyone give me further insight into how to debug this problem?
I ended up figuring out where my issue was. The timezone on my database server was incorrect (6 hours behind my production server).

Saving a document to SharePoint brings up "Web File Properties" dialog with incorrect metadata

Situation:
A custom "Master Document" content type inherits from Document
The "Master Document" content type has five additional choice fields
There are five custom "Document Template" content types that inherit from the "Master Document" content type
Each of the "Document Template" content types uses a different Word document template (.dot) file
Each of the "Document Template" content types have been added to a document library
Problem:
I click on a document in the library
Document opens up in Word 2003 for me to edit
I make some changes and save
A box pops up called "Web File Properties". The window contains all of my custom metadata properties and the ContentType field. The ContentType field is set correctly to the current content type. The other fields are reset to their default values. This same window can apparently be opened by going to File -> Properties
This window by itself would be fine except for two reasons:
It includes the ContentType column
All of my custom metadata properties are visible but are reset to their default values instead of whatever values were previously selected. This means, every time the user wants to save the document, they have to remember what properties were tagged and set them back.
Question:
Can I disable this Web File Properties box?
If no... can I get the fields that show up to be populated to their correct values?
If no... is there a way to disable my fields from displaying in this window?
If no... is this a SharePoint page that I can modify?
***Edit with some more information***
It looks like this only happens in Office 2003 and looks like it affects Choice fields. If I create the same column as a Lookup field, it seems to work.
Edit again
Looks like if the lookup field is a multi-select field then it will not show up in the Web File Properties box at all (single select lookups still work).
edit 10/14/2009
Link to the KB Article mentioned below by Brenda:
http://support.microsoft.com/kb/971500/
This is more of a workaround rather than an answer but I figured I might as well put it here in case it helps someone else.
It seems as if these issues with the Web File Properties box is specific to Office 2003. The issues I reported above seem to be fixed in Office 2007.
If you want to get it working in 2003 and you have choice/lookup fields in your Document content type, here is the summary:
Single select Choice fields DO NOT work
Multi select Choice fields DO work
Single select Lookup fields DO work
Multi select Lookup fields DO NOT work
FYI - I want to CORRECT my previous post. The fix DID FIX my problem after I deleted my internet cache. Works PERFECT now. Here is the KB you need: KB971500 I can email you the fix if you can't find it. The notes in the document do not describe the problem exactly as I would have, but it was the fix for my case.
bhartson#lbrealty.com
We have the EXACT problem. I've opened a case with Microsoft back in February and they were able to finally duplicate my problem.
I have been kept informed and told that my fix would be available with the JUNE cumulative upates. I just received a specific hotfix from my Microsoft rep and applied it and it still did NOT fix my problem. I am hoping he gave me the wrong one and has the real one to send me.
Thanks for your post. I'm may try some of your suggestions above but I just want Microsoft to fix this. We can't upgrade to Office2007!
Thanks.
man, this was really killing me, I spent an entire day recreating document libraries and all sorts of content-types and variations of my excel template before I figured this was a bug... At least MS has a little hotfix request thing now... they're going to send it to me I guess :\
I didn't test this in excel/office 2003 and really botched a presentation of our little workflow... embarassing... always test with the app & environment people are going to use!!!
thanks for the KB article number

Resources