Error Message

Support for our integrated Contact Manager, Calendar, and Project Tracker.
Posts: 32
Joined: Mon Jul 08, 2013 9:43 am
PostPosted: Fri Jul 12, 2013 6:47 am
I just recently got this pop-up while trying to omit different status'. What does this mean?

Capture.JPG
Capture.JPG (22.16 KiB) Viewed 14369 times
SeedCode Staff
SeedCode Staff
Posts: 691
Joined: Mon Feb 28, 2011 2:47 pm
PostPosted: Fri Jul 12, 2013 9:09 am
Hi Illysa,

This error is usually from a problem with the field mapping set-up on the "Source No x" Layout or the Source set up in the script: Load Source Settings at Startup --- Describe Your Sources Here ---

These two set-ups are used to build a SQL query to return the appropriate events by date range and filters. If the Query throws an error, then we show this error.

I would check those sections against the stock copy and make sure everything looks right.

Let us know if that helps,
-Jason
Posts: 1
Joined: Tue Feb 25, 2014 8:11 am
PostPosted: Tue Feb 25, 2014 2:54 pm
I just ran into this same problem and can't seem to get it right.

The $$sc_Query1 is:
SELECT a."zscTimestampStartCalcNum", ''||a."id", a."start_date", a."date_due", a."start_time", a."end_time", ''||a."id_project" , 1, a."zscTimestampEndCalcNum" FROM "SampleEvents" a where a."id_project" LIKE '%465%' and a."zscTimestampStartCalcNum" Between 63526291200 and 63529919999
Union
SELECT a."zscTimestampStartCalcNum", ''||a."id", a."start_date", a."date_due", a."start_time", a."end_time", ''||a."id_project" , 1, a."zscTimestampEndCalcNum" FROM "SampleEvents" a where a."id_project" LIKE '%465%' and a."zscTimestampEndCalcNum" Between 63526291200 and 63529919999
Union
SELECT a."zscTimestampStartCalcNum", ''||a."id", a."start_date", a."date_due", a."start_time", a."end_time", ''||a."id_project" , 1, a."zscTimestampEndCalcNum" FROM "SampleEvents" a where a."id_project" LIKE '%465%' and a."zscTimestampStartCalcNum" < 63526291200 and a."zscTimestampEndCalcNum" > 63529919999
Union
SELECT c."zscTimestampStartCalcNum", ''||c."id", c."meeting_date", c."meeting_date", c."time_start", c."time_end", ''||c."id_project" , 3, c."zscTimestampEndCalcNum" FROM "SampleMeeting" c where c."id" LIKE '-----' and c."zscTimestampStartCalcNum" Between 63526291200 and 63529919999
Union
SELECT c."zscTimestampStartCalcNum", ''||c."id", c."meeting_date", c."meeting_date", c."time_start", c."time_end", ''||c."id_project" , 3, c."zscTimestampEndCalcNum" FROM "SampleMeeting" c where c."id" LIKE '-----' and c."zscTimestampEndCalcNum" Between 63526291200 and 63529919999
Union
SELECT c."zscTimestampStartCalcNum", ''||c."id", c."meeting_date", c."meeting_date", c."time_start", c."time_end", ''||c."id_project" , 3, c."zscTimestampEndCalcNum" FROM "SampleMeeting" c where c."id" LIKE '-----' and c."zscTimestampStartCalcNum" < 63526291200 and c."zscTimestampEndCalcNum" > 63529919999 ORDER by 1

It looks normal and I've compared it to the stock copy of the calendar and still no luck. If you could direct me to the right script or procedure to debug this that would be awesome.
I've already made sure that the field mapping is correct.

Thanks!!
SeedCode Staff
SeedCode Staff
Posts: 475
Joined: Wed Jan 02, 2013 11:47 am
PostPosted: Tue Feb 25, 2014 3:48 pm
Make sure your primary and foreign key fields are all Text fields and see if that helps. If not, send me your files at [email protected] with full-access login information and I'll have a look.
Posts: 1
Joined: Mon Sep 22, 2014 10:47 am
PostPosted: Mon Sep 22, 2014 10:50 am
Running into this same issue - do you have an update on what solved your problem?
SeedCode Staff
SeedCode Staff
Posts: 475
Joined: Wed Jan 02, 2013 11:47 am
PostPosted: Mon Sep 22, 2014 1:41 pm
Hi Garrett. Did you make sure your primary and foreign key fields are all Text fields? If that's not it, send your files to me at [email protected] (with full-access login information) and I'll see if I can help you figure it out. -Jeff

Return to SeedCode Calendar

Who is online

Users browsing this forum: No registered users and 2 guests

cron
(855) SEEDCODE
[email protected]
Follow us: