Urgent: Default Value not showing

[Anon Anon]

Hi, [left] [left] this is urgent. [left] [left] We created attributes with Money Data type.   all these new attributes defaulted value of 0.000 is not showing on the created page.   [left] The Object fields, default value is also updated with 0.000 and again not showing. [left] [left] What also interesting is that when tried to change the 0.000 default value  to just 0 or 0.00, the system will not save.   the only way will save is leaving the default value blank.   But, we don't want it blank because a newly created portlet  calculations depend on all these fields.   So if one of these entered fields are left blank the new portlet will not pick up the rest of the entered values.   We don't want to make all the fields as required fields to the users either. [left] [left] Any suggestions why the Default value is not showing? [left] [left] thank you! [left]

Attachment(s)

1.doc   87 KB 1 version

[Anon Anon]

Please try setting default value and 'value required' at 'view level' not 'attribute level' (see attached) - does this help?  If not please mention the version of Clarity you use  (and database type)    

Attachment(s)

money-attribute-default-and-required.doc   104 KB 1 version

[Anon Anon]

Hi,  yes, I set the 0.000 and value required at object fields view, but in the display screen now the Value Required is identified which  don't want.  I don't understand your screen #4 and #5.either way, 0.000 is set at attribute level like you said and 0.000 w/ value required checked at view level.see attachment.  We are using version 8.1, SQL, windows server 2003.  NOTE: I contacted CA support and they said this is probably a known bug but has not confirmed yet.any advice would really appreciate.

Attachment(s)

Doc 3.doc   80 KB 1 version

[Anon Anon]

Ok - misunderstood your original post. You want to store zero (not null) but not make these attributes required.  If support suggest this is a bug in your version - then I would suggest you need to revise the portlet logic so that if the field is null, it is treated as zero instead.  mssql: isnull(field,0)oracle: nvl(field,0)  e.g.  select    id  , isnull(needed_numeric1,0) as needed_numericfrom table    

[ybus]

If your problème is  to have your calculated field work with null value and not just to display 0, you can set  them so that it handle the null value.  To do so, try to replace the reference to your attribute (lets call it X) by Max(X,0).  It is import to put the 0 at the second place... according to my test, for Clarity Max(null,0) = 0 but Max(0,null)=null...  Hope this help.  Ybus

[Anon Anon]

Thanks Paul and ybus!  unfortunately, I am a horrible programmer and don't want to mess up the query.  but guess what, I found the soln.take out the manual input 0.000 in both attribute and view level.then in attribute page add 0 to the Default field and check the Populate null value w/ default checkbox.as soon as save/submit, the system change the 0 to 0.000 and display in the new created page all the new fields.    

[Sriraj Silla]

I have done the following..

1. Made the input fields as 'Value Required'

2. In the views, i've made the fields in create/edit layouts as Hidden.

 

If the above steps are implemented, the user gets a message saying 'All required fields need to be filled out' in the List Layout if any input fields are left blank.

[Suman Pramanik]

Can you please make it visible and see if you can filter.

[Deactivated User]

Please explain. That is exactly what is to be expected when you make fields required. Hiding he fields do not hide the problem.

[Sriraj Silla]

I was just trying to prevent NULLs being passed by the user.

[David Morton]

Sriraj.silla wrote:

 

I was just trying to prevent NULLs being passed by the user.

You need to be providing default value(s) then, not making fields required (mandatory)