slxdeveloper.com Community Forums

The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!

Web Forums - SalesLogix Web Client (Pre-7.2)
Forum to discuss using & developing the legacy SalesLogix Web Client (For versions 7.0 and earlier). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix Web Client (Pre-7.2) | New Thread

View: Search:

Author

Thread: Error: Invalid date fomat detected. Valid date format is: M/d/yyyy

David Nunnally
Posts: 206

Error: Invalid date fomat detected. Valid date format is: M/d/yyyy Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 10 Jul 06 11:29 AM

This is comming from the action genoppsnapshot. The Summary section (Opened x days ago on x/x/xxxx) uses the alias dateopen (opportunity.dateopened). This only occurs on certain opps and not others. A few of the opps giving the error have the values...
---2003-08-06 05:00:00.000
---2005-03-10 14:34:09.000
---2005-04-28 19:30:57.000
in the dateopened field. Any idea why the web client thinks these are invalid date formats?

[Reply][Quote]

Snow Monkey
Posts: 214

Re: Error: Invalid date fomat detected. Valid date format is: M/d/yyyy Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 13 Jul 06 4:12 PM

I have received the same error message;but it was a diff scenario

i changed the short data format in the control panel to MM/dd/yyyy and restarted the machine.Then used format =3 formatstring =ddddd to show the short Data format of the Web Host.

hope this helps!

[Reply][Quote]

David Nunnally
Posts: 206

Re: Error: Invalid date fomat detected. Valid date format is: M/d/yyyy Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 14 Jul 06 8:17 AM

I found the problem. Had nothing to do with the date directly. Found out certain records do not exist in all custom addon tables. Thanks to some idiot before me! When an alias used on the oppinfo page was from one of those tables the page stopped processing and each of the remaining values were null including the date. Hence invalid date format. Ran some scripts and populated all addon tables with default data. Problem solved. I do wish it was easier to debug the web client!

Thanks for your reply Nandu.

[Reply][Quote]

Jeff Ballard
Posts: 326

Re: Error: Invalid date fomat detected. Valid date format is: M/d/yyyy Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 14 Jul 06 10:43 AM

David,

You mentioned that you ran scripts to populate the data in the missing tables. Have you updated (don't know if it's necessary) any web actions to insert data into the 1:1 tables when records are added? Otherwise, in a few weeks you may find yourself in the same situation again.

Jeff

[Reply][Quote]

David Nunnally
Posts: 206

Re: Error: Invalid date fomat detected. Valid date format is: M/d/yyyy Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 14 Jul 06 10:55 AM

Good point. Luckily that can wait. I am only allowing viewer only users access to the thin client once I am finished. We have 50 viewer only licenses and never installed the thin client and a lot of users using a license just to lookup info. We have years of mods that I am having to add to the thin client prior to 7-28 roll-out. I am just adding simple single item picklist etc. that require no additional scripting for this and adding text for the rest. Next year I may go back and update the tabs for read/write access and allow all users access once I catch up on all my projects.

[Reply][Quote]

Page 1 of 1

You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 2/19/2025 4:31:43 PM