Re: ARERR 120039 - operation violates the cardinality constraint...

2011-10-07 Thread Gerard Lafontant
** ** ** ** *De:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *En nombre de *Gerard Lafontant *Enviado el:* Miércoles, 05 de Octubre de 2011 17:49 *Para:* arslist@ARSLIST.ORG *Asunto:* ARERR 120039 - operation violates the cardinality constraint...* *** ** ** ** Anyone

ARERR 120039 - operation violates the cardinality constraint...

2011-10-05 Thread Gerard Lafontant
Anyone has seen this error before? and what's a possible fix on this issue? thank you all in advance. The operation violates the cardinality constraint of the relationship. : 1-Many cardinality will be violated. Cannot create relationship instance because right endpoint is already in another

Field Value to be Reset on Copy to New Operation

2011-06-06 Thread Gerard Lafontant
Any help on how to go about creating this below? Field Value to be Reset on Copy to New Operation When a user is looking at an existing record and they either select the “Copy to New” option from the “Edit” menu or press the CTRL+T key combination to initiate a “Copy to New” function, the

Re: Field Value to be Reset on Copy to New Operation

2011-06-06 Thread Gerard Lafontant
/ -- *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Gerard Lafontant *Sent:* Monday, June 06, 2011 11:57 AM *To:* arslist@ARSLIST.ORG *Subject:* Field Value to be Reset on Copy to New Operation ** Any help on how

Field Value must be Unique - Unique Index

2011-06-03 Thread Gerard Lafontant
All, In creating a filter (i'd assume) to prevent no two records in a form field name not to have same value (Unique Index) stored in that field, what Qualifications and If Action needed in order to make that happens thanks

Re: Field Value must be Unique - Unique Index

2011-06-03 Thread Gerard Lafontant
Not allow to change the properties on the field. has to be workflow built... On Fri, Jun 3, 2011 at 4:27 PM, jham36 jha...@gmail.com wrote: ** Could't you just create a unique index for that field on the form in the admin tool or Dev Studio (in Form Properties)? James _attend WWRUG11

needs immediate help on this query....

2011-05-20 Thread Gerard Lafontant
All, Can anyone tell me what am i missing or is wrong from this query that's causing the filter not to fire (by pass) on new request; and only fires on modified existing request. Basically, i'm forcing user to keep away from using 'Closed' Status resolution and push them to use the

Re: needs immediate help on this query....

2011-05-20 Thread Gerard Lafontant
) OR ('DB.Status' = Cancelled) OR (‘DB.Status’ = $NULL$)) AND ('Status' = Closed) Hope this fixes it. Thanks! Greg *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Gerard Lafontant *Sent:* Friday, May 20, 2011 10:59 AM *To:* arslist

Re: needs immediate help on this query....

2011-05-20 Thread Gerard Lafontant
this: (($OPERATION$ = SET AND (('DB.Status' Resolved) OR ('DB.Status' = Cancelled))) OR ($OPERATION$ = CREATE) ) AND ('Status' = Closed) On May 20, 10:59 am, Gerard Lafontant gelaf...@gmail.com wrote: All, Can anyone tell me what am i missing or is wrong from this query that's causing the filter