For those that are having trouble with the "View Relationships" feature I would persevere if you can. I know that it only works if your server is 7.5 and it is enabled but it is probably the single best feature for me in DS.
I'm finding that an enormous amount of the opening of workflow is from the relationships list. Having the form I'm working on open and then using the fields and buttons etc. to locate the appropriate workflow is a far more intuitive way for me than the old way where I had to locate workflow by naming convention. The big clincher is that by doing a show relationships on an active link or filter I can now find the guides that reference it. I'd have to say that this feature is the single best thing about DS. I've hardly used the "undo" but I'm using the view relationships all the time. One suggestion I have for it though is that the workflow order number would be a very handy column to have in the relationship list. Rod 2010/1/8 Jason Miller <[email protected]>: > ** Ok, so I am not crazy. I was trying to add a form to an application > yesterday it it just wouldn't take. > > I agree patch 3 is getting there. The adding new fields to set/push fields > not taking the first time is gets old fast. I am afraid to do the initial > load of building the relationships. But in general I LOVE the Dev Studio. > <3 > > Jason > > On Thu, Jan 7, 2010 at 3:57 PM, Rod Harris <[email protected]> wrote: >> >> Hi, >> Yes this is a problem with patch 3 of DS. I have found that you need >> to do 2 things to avoid using the old admin tool for editing some >> qualifications. >> >> 1. Use the button to open up the expression editor. >> 2. Replace all enums with their numeric equivalent. (Not just the new >> one.) >> >> Failing to do both of these will give you the error message. >> >> I currently need to use the admin tool for 2 things in patch 3. >> >> 1. Search menus that reference fields on the form hosting the menu >> 2. Adding new forms to applications. >> >> On the bright side patch 3 seems to fix issues I had earlier with >> table field qualifications. >> >> For some reason I have issues adding new fields to set field and push >> field actions. Quite often they don't take on the first attempt. >> >> I love the "show relationships" feature and now use it all the time to >> locate workflow to modify. >> >> Rod >> >> 2010/1/8 Lyle Taylor <[email protected]>: >> > I’ve seen errors numerous times where DS thought that the value >> > specified in >> > a qualification for an Enumeration was not valid, even when it did like >> > you >> > said and replaced a numerical value with the label itself. I get a >> > different error than what you reported (something along the lines of the >> > value not being valid), but still get an error. I have not found a way >> > to >> > work around it except to use the Admin tool to make the change instead >> > (we’re still on ARS 7.1, so the Admin tool is still an option when >> > necessary). If you or someone figures out how to deal with this, I’d >> > love >> > to know the answer. >> > >> > >> > >> > Lyle >> > >> > >> > >> > From: Brien Dieterle [mailto:[email protected]] >> > Sent: Thursday, January 07, 2010 4:34 PM >> > To: [email protected] >> > Cc: Lyle Taylor >> > >> > Subject: Re: Data types are not appropriate for relational operation, >> > 313, >> > error message >> > >> > >> > >> > I just started getting this error and happened to notice this thread. I >> > was >> > definitely fiddling with the enumeration numbers on several fields on a >> > custom form. >> > >> > AR System 7.5 P3, Dev Studio 7.5 P3 on Windows 7 >> > >> > The oddest thing is, I can add any singular clause like "FieldX = 0" A >> > moment later it will resolve that to "FieldX = "Yes". I can save it >> > just >> > fine. However, if I add another clause such as "AND FieldY = 0" It >> > will >> > resolve that and upon save get the error. And yet FieldY = 0, by >> > itself, >> > does not produce the error. In fact, duplicating a clause causes the >> > error >> > as well (FieldX = 0 AND FieldX = 0). So it seems it is merely having 2 >> > or >> > more clauses that causes the problem, not a resolution or caching >> > problem... >> > >> > >> > I've deleted my entire devstudio wkspace folder... >> > I've tried making an entirely new filter, same problem >> > I've tried an entirely new filter on a different form that I haven't >> > modified lately-- same problems. >> > >> > I'll have to start down the restarting things path... >> > >> > Brien >> > >> > On 1/7/2010 3:43 PM, Lyle Taylor wrote: >> > >> > Do you have the most recent patch version of Developer Studio? I >> > haven’t >> > run into this particular problem yet, and I have changed labels before, >> > but >> > maybe I just haven’t done this particular scenario yet. >> > >> > >> > >> > I wouldn’t be surprised if it is related to the fact that DS caches >> > objects >> > you’ve opened to disk. I have seen where the cache is out of date or >> > otherwise inaccurate, and that has caused me grief. The fix was to >> > delete >> > the files that DS created in the workspace directory and then reopen the >> > object. I suspect that there are issues around how DS determines >> > whether >> > the cached object is correct/up to date. >> > >> > >> > >> > Lyle >> > >> > >> > >> > From: Action Request System discussion list(ARSList) >> > [mailto:[email protected]] On Behalf Of Kelly Deaver >> > Sent: Thursday, January 07, 2010 3:33 PM >> > To: [email protected] >> > Subject: Re: Data types are not appropriate for relational operation, >> > 313, >> > error message >> > >> > >> > >> > ** >> > >> > Did you change the labels on any of your enums? I hit this all the time >> > if I >> > changed something. >> > >> > >> > >> > Example - >> > >> > A filter was created with a Qualification of Status < "Work In >> > Progress". >> > You changed the enum 7 from "Work In Progress" to "Development in >> > Progress". Now you open a filter that included this qualification and >> > look >> > at the qualification.. Guess what, it still says "Work In Progress". As >> > long as you don't touch the qualification you can still save the filter. >> > Once you touch the qualification, even to add another clause, then >> > Developer >> > Studio checks that the qualification is valid.. which it isn't because >> > it >> > didn't properly translate the enum to words. You have to edit the >> > Qualification and say Status < 7 which will get it to resolve to >> > Development >> > in Progress and now you can happily save.. >> > >> > >> > >> > This is frustrating.. Is it just me or did Admin Tool do this properly >> > and >> > translate the enum label for you when you opened the Filter for >> > editing???? >> > >> > >> > >> > Kelly Deaver >> > >> > [email protected] (ARSlist mail) >> > >> > >> > >> > >> > >> > -------- Original Message -------- >> > Subject: Re: Data types are not appropriate for relational operation, >> > 313, error message >> > From: Kevin Begosh <[email protected]> >> > Date: Thu, January 07, 2010 11:13 am >> > To: [email protected] >> > >> > ** >> > >> > Sorry I meant to say this before I sent it out. I seems like it is only >> > happening on one of our environments, one developer tool etc... Any >> > reason >> > anyone know why this would be happening. What is wrong with that >> > environment that the developer tool would be mistaking on selection >> > values, >> > I guess more so not recognizing them? >> > >> > >> > >> > Kevin >> > >> > On Thu, Jan 7, 2010 at 12:02 PM, Kevin Begosh <[email protected]> wrote: >> > >> > List, >> > >> > I am on 7.5 and I noticed that I am getting these error messages quite >> > frequently when working with our of the box selection fields. Has >> > anyone >> > else been getting these. For example I am working with filter >> > >> > >> > >> > RQC:REQ:RequesterInfo_080_SetRequestedBytoRequestedFor >> > >> > >> > >> > and all I want to do is add an additional item to the run if so that >> > does >> > not fire for a specific instance I am setting it to. When I try to save >> > my >> > changes I keep getting that error message >> > >> > >> > >> > Data types are not appropriate for relational operation, 313, >> > >> > It looks like the out of the box code is getting the error message. >> > >> > >> > >> > For instance if you go in that filter and change one of the selection >> > fields >> > to a different value, such as 'UnknownUser' from False to True I get >> > that >> > error message. >> > >> > >> > >> > Is there something querky going on with 7.5, is it something with the >> > server >> > I am on, or the developer tool etc.... >> > >> > >> > >> > I never got these on the admin tool prior to 7.5 >> > >> > >> > >> > Env: windows 2003 server, AR Server 7.5, ITSM 7.5 >> > >> > -- >> > Kevin Begosh >> > >> > >> > -- >> > Kevin Begosh >> > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers >> > Are"_ >> > >> > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers >> > Are"_ >> > >> > NOTICE: This email message is for the sole use of the intended >> > recipient(s) >> > and may contain confidential and privileged information. Any >> > unauthorized >> > review, use, disclosure or distribution is prohibited. If you are not >> > the >> > intended recipient, please contact the sender by reply email and destroy >> > all >> > copies of the original message. >> > >> > >> >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" > > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
