23
Jun
2009
Siebel – Make MVG Field required – II
by Nitin JainHi friends,
This is a follow-up post of the post by Prachi yesterday about making an MVG field Required. You can read the post here. Yes, this truly is an issue in development as the straight OOB methods don’t seem to work at first. However, I personally am quite strongly against scripting in any case anyways!
Nice work, Prachi. But, I feel we may be able to implement the same requirement by simple configuration. Just that it is not so evidently displayed at first.
Try this:
Original Field Name: “Dummy Field”
Create a new calculated field with the following details:
| Name: | “Dummy Field 2″ (We can actually play with Name/Display Name to make it meaningful) |
| Calculated Value: | [Dummy Field] |
| Force Active: | TRUE |
| Required: | TRUE |
You should now see a proper error message whenever a user tries to save a record with NULL values in the field, “Dummy Field”. The error message will, however, point to this new Calculated field. Cheers!
Related posts:
- Siebel – Make MVG Field required Siebel supports the concept of Multi Valued Fields, or the...
- Siebel – Showing red asterisk on a conditionally required field In Siebel vanilla Application, we see a red asterisk (...
- Siebel – Make a field Required, conditionally There was a requirement in our project to make Account...
- Siebel – HTML Code displayed in Error Message There was a requirement in our project to make Account...
- Siebel – InvokeServiceMethod() on Calculated Fields InvokeServiceMethod() is used to invoke Business Services and take values...
- Query on the Long Column or Field A typical problem in any EAI project. Others too!! One...
- Siebel – Left, Right and from the Middle Extracting a sub string from a lengthy string in Siebel....
Pretty nice post. I just found your blog and wanted to say
that I’ve really enjoyed reading your blog posts. In any case
I’ll be subscribing to your feed and I hope you post again soon!
This idea of making MVF works only for first time.This fails when you remove the value from the field and save the record.You will not get pop up message this time.
eg: On Accounts, suppose you make Contact MVF required through some calculated value say Contact Calc. When you create a new record in Accounts and do not associate Contact with Account, you will receive a pop up message saying Contact is a required Field.You associate Contact with Account and save the record.Now go on Contact field and remove the Contact you associated with Account.Save the record.You will not receive any pop up message.Strange is n’t it!
I searched for this problem in support web and found this to be a product defect.
The only way left is to do scripting on BC Pre Write record function to achieve the desired result.
hmmm.. seems to be strange. Have you actually tried this out yourself, Madhvi?
Also, in case this is not working, can you share your solution with everybody as well please, if it’s different from what Prachi suggested?
Also, please do post the Metalink which says this. Guess it would help everybody out there.
I have tried this out and this does not work.Please refer to posting “Doc ID 509328.1″ on Metalink.