Re: Push Field Problem

[Bhagawat, Prashanth]

Hi, 
 
Some of the possibilities are listed below, due to which Radio button
selected value is not getting passed from the display only for to you
Data storage form.
 
1. You might have copied the Radio button field from the Display only
form to your Regular form, by default then Entry Mode for the field
might have been Display Only.
 
2. If you are using Push values by Matching Id, and you have got
different field ids for the Radio Button( on both forms ) , one to that
of the Display Only form & to that of the Regular Form.
 



Regards, 

Prashanth Bhagawat 


 



From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Sokol, Brian
Sent: Saturday, May 12, 2007 12:41 AM
To: arslist@ARSLIST.ORG
Subject: Push Field Problem


** 

Hi All, 

I have a Display Only form where I am pushing several fields to another
table. Everything works OK except one field called Component Needed.
This field is a Radio Button Field with a Custom ID Enumeration (values
are 10, 20, 30 etc). I have the same radio button field on both the
display only form and the other form that I am trying to push the values
to. Nothing is getting pushed from the radio button field. Here is a bit
of the active link log:

True actions: 
 action 0 
  Push-fields 536870962 = 20 

It shows that an ID of 20 is being pushed to the radio button field and
yet when I look at that record that field has no value. Anyone have any
ideas?

thanks 

Brian Sokol 
Manager, Desktop Services 
Scholastic Inc. 
557 Broadway 
NY, NY 10012 
(212) 343-6494 
http://www.Scholastic.com <http://www.Scholastic.com>  

__20060125___This posting was submitted with HTML in
it___


This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Re: Push Field Problem

[Jason Miller]

Maybe a bit on the obvious side but is the is the field on the data form
Display Only? Is it possible that the field was copied from the DO form and
Entry Mode was not changed from Display Only?

 

Jason

 

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Sokol, Brian
Sent: Friday, May 11, 2007 12:11 PM
To: arslist@ARSLIST.ORG
Subject: Push Field Problem

 

** 

Hi All, 

I have a Display Only form where I am pushing several fields to another
table. Everything works OK except one field called Component Needed. This
field is a Radio Button Field with a Custom ID Enumeration (values are 10,
20, 30 etc). I have the same radio button field on both the display only
form and the other form that I am trying to push the values to. Nothing is
getting pushed from the radio button field. Here is a bit of the active link
log:

True actions: 
 action 0 
  Push-fields 536870962 = 20 

It shows that an ID of 20 is being pushed to the radio button field and yet
when I look at that record that field has no value. Anyone have any ideas?

thanks 

Brian Sokol 
Manager, Desktop Services 
Scholastic Inc. 
557 Broadway 
NY, NY 10012 
(212) 343-6494 
 <http://www.Scholastic.com> http://www.Scholastic.com 

__20060125___This posting was submitted with HTML in
it___


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Push Field Problem

[Sokol, Brian]

Hi All,

I have a Display Only form where I am pushing several fields to another
table. Everything works OK except one field called Component Needed.
This field is a Radio Button Field with a Custom ID Enumeration (values
are 10, 20, 30 etc). I have the same radio button field on both the
display only form and the other form that I am trying to push the values
to. Nothing is getting pushed from the radio button field. Here is a bit
of the active link log:

True actions:
 action 0
  Push-fields 536870962 = 20

It shows that an ID of 20 is being pushed to the radio button field and
yet when I look at that record that field has no value. Anyone have any
ideas?

thanks

Brian Sokol
Manager, Desktop Services
Scholastic Inc.
557 Broadway
NY, NY 10012
(212) 343-6494
http://www.Scholastic.com


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Re: Push Field Problem

[Thomas Bean]

There is a bug related to this, I can't remember if it was corrected in a 
5.1.2 patch or in version 6.x possibly...


Essentially, the $DATE$ keyword is resolving to Unix epoch seconds instead 
of the correct value for date fields (# of days since Jan 1, 4713 B.C.).  As 
I recall, the bug only affected using $DATE$ in a workflow qualification 
with a date field (the $DATE$ keyword should work correctly as a set fields 
value for a date field).


I believe the workaround I used was to set a hidden display-only date field 
to $DATE$, then use this field in place of the $DATE$ keyword in the 
qualification.  For example:


Set Fields:
'zTmpDate' = $DATE$

Subsequent 'Push Field If':
( 'Submitter' = $USER$) AND ( 'Sign In Date' = 'zTmpDate')

HTH,

Thomas

- Original Message - 
From: "Sokol, Brian" <[EMAIL PROTECTED]>

Newsgroups: gmane.comp.crm.arsystem.general
Sent: Monday, October 30, 2006 11:43
Subject: Re: Push Field Problem


It is a Date field. They strange thing is I just noticed that this works
ok from the web. If I use aruser it creates a record every time. Either
I am misinformed about something or this is a bug.

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bean
Sent: Monday, October 30, 2006 12:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: Push Field Problem

Brian,
Is the 'Sign In Date' field a date/time field or a date field?  If it is

date/time (even if it is only set to display as date-only), then your
qualification would only prevent multiple requests from being created
for
the current user for given second of the day, *not* for the given day.

If this is the cause, you should be able to correct this without
converting
to the date field type by using this modified qualification:

( 'Submitter' = $USER$) AND ( 'Sign In Date' >= $DATE$)

HTH,

--Thomas

- Original Message - 
From: "Sokol, Brian" <[EMAIL PROTECTED]>

Newsgroups: gmane.comp.crm.arsystem.general
Sent: Monday, October 30, 2006 11:11
Subject: Push Field Problem


I am trying to create some simple time auditing based upon when forms
are opened. I am running an AL with a push fields action to a form. I
set the Push Field If to:
( 'Submitter' = $USER$) AND ( 'Sign In Date' = $DATE$)
And set If No Requests match to Create a New Request
And
If Any Request Match to Take No Action.

Every time I open the form that triggers this AL it creates a new record
even though there are multiple records with my account in the Submitter
field and today's date in the Sign In Date field.

What am I doing wrong?

Brian Sokol
Manager, Desktop Services
Scholastic Inc.
212-343-6494
[EMAIL PROTECTED]
<http://www.scholastic.com>


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Re: Push Field Problem

[Sokol, Brian]

I just noticed this AL works as I thought it should from the web. If I
use the User tool it creates a new record every time. I am on ver 7.0
for aruser, server and MidTier. 

Also noticed that if I switch the Push Field If statement to:
( 'Submitter' = $USER$) AND ( $DATE$ = 'Sign In Date') 

I get an arerror 313 Data types are not appropriate for relational
operation

-Original Message-
From: Sokol, Brian 
Sent: Monday, October 30, 2006 12:12 PM
To: arslist@ARSLIST.ORG
Subject: Push Field Problem

I am trying to create some simple time auditing based upon when forms
are opened. I am running an AL with a push fields action to a form. I
set the Push Field If to:
( 'Submitter' = $USER$) AND ( 'Sign In Date' = $DATE$)
And set If No Requests match to Create a New Request
And
If Any Request Match to Take No Action.

Every time I open the form that triggers this AL it creates a new record
even though there are multiple records with my account in the Submitter
field and today's date in the Sign In Date field.

What am I doing wrong?

Brian Sokol 
Manager, Desktop Services 
Scholastic Inc. 
212-343-6494 
[EMAIL PROTECTED] 
<http://www.scholastic.com> 

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Re: Push Field Problem

[Sokol, Brian]

It is a Date field. They strange thing is I just noticed that this works
ok from the web. If I use aruser it creates a record every time. Either
I am misinformed about something or this is a bug. 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bean
Sent: Monday, October 30, 2006 12:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: Push Field Problem

Brian,
Is the 'Sign In Date' field a date/time field or a date field?  If it is

date/time (even if it is only set to display as date-only), then your 
qualification would only prevent multiple requests from being created
for 
the current user for given second of the day, *not* for the given day.

If this is the cause, you should be able to correct this without
converting 
to the date field type by using this modified qualification:

( 'Submitter' = $USER$) AND ( 'Sign In Date' >= $DATE$)

HTH,

--Thomas

- Original Message - 
From: "Sokol, Brian" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.crm.arsystem.general
Sent: Monday, October 30, 2006 11:11
Subject: Push Field Problem


I am trying to create some simple time auditing based upon when forms
are opened. I am running an AL with a push fields action to a form. I
set the Push Field If to:
( 'Submitter' = $USER$) AND ( 'Sign In Date' = $DATE$)
And set If No Requests match to Create a New Request
And
If Any Request Match to Take No Action.

Every time I open the form that triggers this AL it creates a new record
even though there are multiple records with my account in the Submitter
field and today's date in the Sign In Date field.

What am I doing wrong?

Brian Sokol
Manager, Desktop Services
Scholastic Inc.
212-343-6494
[EMAIL PROTECTED]
<http://www.scholastic.com>


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Re: Push Field Problem

[Thomas Bean]

Brian,
Is the 'Sign In Date' field a date/time field or a date field?  If it is 
date/time (even if it is only set to display as date-only), then your 
qualification would only prevent multiple requests from being created for 
the current user for given second of the day, *not* for the given day.


If this is the cause, you should be able to correct this without converting 
to the date field type by using this modified qualification:


( 'Submitter' = $USER$) AND ( 'Sign In Date' >= $DATE$)

HTH,

--Thomas

- Original Message - 
From: "Sokol, Brian" <[EMAIL PROTECTED]>

Newsgroups: gmane.comp.crm.arsystem.general
Sent: Monday, October 30, 2006 11:11
Subject: Push Field Problem


I am trying to create some simple time auditing based upon when forms
are opened. I am running an AL with a push fields action to a form. I
set the Push Field If to:
( 'Submitter' = $USER$) AND ( 'Sign In Date' = $DATE$)
And set If No Requests match to Create a New Request
And
If Any Request Match to Take No Action.

Every time I open the form that triggers this AL it creates a new record
even though there are multiple records with my account in the Submitter
field and today's date in the Sign In Date field.

What am I doing wrong?

Brian Sokol
Manager, Desktop Services
Scholastic Inc.
212-343-6494
[EMAIL PROTECTED]
<http://www.scholastic.com>

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Push Field Problem

[Sokol, Brian]

I am trying to create some simple time auditing based upon when forms
are opened. I am running an AL with a push fields action to a form. I
set the Push Field If to:
( 'Submitter' = $USER$) AND ( 'Sign In Date' = $DATE$)
And set If No Requests match to Create a New Request
And
If Any Request Match to Take No Action.

Every time I open the form that triggers this AL it creates a new record
even though there are multiple records with my account in the Submitter
field and today's date in the Sign In Date field.

What am I doing wrong?

Brian Sokol 
Manager, Desktop Services 
Scholastic Inc. 
212-343-6494 
[EMAIL PROTECTED] 
 

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"