ca.portal.admin

Weird IDD behavior

Discussion created by ca.portal.admin on May 4, 2006
Latest reply on May 4, 2006 by ca.portal.admin
This has happened to me a number of times here, but nowhere else.

I go into the IDD and ADD an element.

IDD 16.0 NO ERRORS
ADD
ELEMENT NAME IS REMINDER-NOTICE-CNT
PUBLIC ACCESS IS ALLOWED FOR ALL
PRIMARY
PICTURE IS 9(05)
.

Then I REPL a record with new element and the element has disappeared!
It seems to take a minute or two for this to happen.

000044 RECORD ELEMENT IS REMINDER-NOTICE-CNT V 1.
000044*+ E DC601012 ELEMENT IS NOT IN DICTIONARY 000044*+ W DC601017
FORWARD SPACING TO NEXT PERIOD

The only way I seem to get the element to stay, is to restrict access to
me only.

Tim Gortner
Sr. Consultant - Sogeti USA LLC
Iowa Department of Human Services
DDM Medical Systems and Data Warehousing
(515) 725-1196

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Weird IDD behavior
"Dan:

The really weird part that happened to me today, was that I ran my IDD
update again a bit later and then all the elements were there. It's
almost like there are mirrored dictionaries that hadn't sync'd up. I'm
not a systems guy, so I don't even know if that's possible.

Tim


----- Original message -----
From: ""Hall, Dan (GE Comm Fin)"" <Dan.Hall@GE.COM>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Thu, 4 May 2006 11:44:35 -0400
Subject: Re: Weird IDD behavior

Tim,
Take a look at your default options for VERSION. I seem to remember
something like this once when a contractor set the default version
number to zero instead of one.

Outcomes