LOV values are not coming into UI - siebel

There is a LOV field (F1) in one of the applet in which values are not coming as you click on it. I checked at 'Administration - data > List of values' and found that for this field, LOV records are created. From tools I have checked all the possible error of configuration due to which the values could not come into the field. However there is no error in configuration. I compared this field (F1) with another field of its type but with this field there is no issues. I don't understand why values are not coming in this field (F1) only
Kindly let me know what are the possible reason's due to which the vaules are not coming. Is it related with postion also? Kindly help.

Use LookupValue(LOV_TYPE, Language_Independent_Code) in Calculated value of a field.
Remember to check "Calculated" flag.
Be sure that LOV value is present in flat LOV screen.
Make sure that Active flag is checked and LOV_TYPE, LIC and Display Value are populated ....
for a given LOV_TYPE and LIC, Display value will be pulled.

First, you can check if the values in the LOV have 'Active' flag checked.
Next , check if the field in the BC has Picklist assigned to it and at lease one Pickmap. If there are multiple pickmaps, check if any one among them has 'Constrain' checked. Finally, in the applet, the 'Run Time' flag must be checked for the picklist to properly work.
If it still does not work, check if any statemaps have been created for them.

Related

Formula help on IF ELSE on Smartsheet

I want to have a condition where IF Delivered column checkbox is checked, then that whole row will be deleted. Is that feasible?
How can I start with it?
Formulas can't change the condition of an item (like a row), only the value in a cell. So, in other words, you can't delete a row with a formula.
You "could" do this with an external script using the Smartsheet API, but you'll want to take situations that #Ken White mentioned in the comments into account. Your script should make sure that there is a way for users to recover the deleted row if the box is checked by mistake.
There are a couple of ways this might be possible. If you set up a default filter on a sheet to always load rows where complete box is unchecked, then, if you checked off a task or two and reloaded the sheet those tasks would not be visible the next time it loads.
To do this:
Create a new filter.
Title it and check the Share Filter checkbox
Set the criteria to the checkbox is unchecked
Then click okay
Save the sheet to save the shared filter.
Click on SHARE
Scroll down and click edit next to the default view
Set the filter to new filter you saved
Save.
Check off some boxes and save the sheet.
Reload the sheet and the completed items will not be visible.

Ideal Siebel EIM component level Log setting

What is the ideal eventlevel log settings for the siebel component "Enterprise Integration Mgr".
The problem is while running the EIM job, I provide the highest value for sqlflag, traceflags and error flags, still I am not getting the detailed log for the PICKLIST_VALUE error, to find the column.
Kindly advise.
Thanks,
Kriti
This issue is faced when there is a LOV value (Bounded Picklist) which is not getting resolved. To resolve this first you need to identify the columns which are populating the LOV i.e picklist or dropdown, then verify that the value being pushed in that column is present in the List Of Values..
If still the error is not resolved then please provide the ifb file details
You can set the below log levels to debug the issue that you are facing.
SQLFlags = 8
ErrorFlags = 1
TraceFlags = 3
Apart from this, you can check the column associated to the Picklist based field. Check the below property in Siebel Tools under for a Column.
LOV Type
LOV Bounded
Translate
If LOV Bounded is TRUE, then, during import, EIM checks the values against the values contained in a list defined in the LOV Type property.
If LOV Type and Translate property is populated, then Siebel stores the LIC value in that particular column for a specific LOV value.
Hope in this way you can track and debug the issue.

Siebel Operation Error for Inserting Field based on picklist

I am facing an issue where I am getting the below error while inserting a record in the table via Siebel Operation step.
Here the error is showing for field which is based on a picklist. Could anyone please suggest why i am getting this error:
SBL-DAT-00225: The value entered in field District of buscomp Contact_Address_LT does not match any value in the bounded pick list PickList Comm Resolution.
SBL-BPR-00100: This error is returned when the workflow/task is executing the Siebel Operation business service.
I am aware that this happens when the value is not defined in the picklist. But i have verified this, and LOV is having the value which I am trying to get insert.
This error is quite common. And could happen for a couple of reason.
As you have mentioned, that you have already checked the value which is getting inserted is already there in the LOV defined for the picklist.
I have recently faced this error, and spent hours to debug it. Try below to sort your problem.
Check for the below points:
1) Check for the pick map for this field, check if any contraint field is also present in it.
2) If yes, then check those constraint field is also getting inserted in same Siebel Operation step. Siebel does not follow sequence in the input argument. So if this is the case do step 3 to resolve your issue.
3) Split the insert statement into 2 parts, 1 where you insert the record with the values which is present in the pick map constraint and then update the same record. This will ensure that all the required field are populated.
Solution from 8.1.1.4 is to add parameter into OM's config file, e.g fins.cfg:
[Task]
ProcessArgAsc = true
More details in my oracle support.

How to make a date field to be autopopulated in Siebel CRM Desktop?

Whenever I create a new activity, I need a date field to be autopopulated ( it will be autopopulated but greyed out until and unless a checkbox next to it needs to be checked).
I perform a validation based on the date field, when a new activity is created. since the date field check box is not checked, it is not considering the value for the validation.
Any help or suggestion is appreciated.
Thanks.
Jaya Vignesh.
make use of predefault and postdefault values to populate current-date.
set field Read-only (BC field user property). You can find it under Business Component in object explorer.
Field read-only allows you to make a field read-only based on value of other field from same BC or joined field.
I perform a validation based on the date field, when a new activity is created. since the date field check box is not checked, it is not considering the value for the validation.
This requirement of yours isn't clear what exactly you want to validate. Since you are populating it bydefault, I don't find the significance in validating your own auto-populated data. well yet I provide a suggestion below
There are two types of validations, 1. Using configuration or 2. Using scripting. I am not pretty much sure if it can be achieved with configuration but scripting it is possible by overriding BusComp_presetFieldValue, BusComp_preWriteValue. The first one executed when you populate a field. And the latter one when you commit the record.
I have answer assuming your requirement. Let me know if you have any questions or clarifications required.
You can add the Predefault property of the field to be the following
System: TimeStamp

I have a field in APEX set with a default of SYSDATE but it does not update

I have a field defined in my table as DATE and want it to automatically populate with the current system date when someone access the update form in my APEX application. But the date doesn't update. It was working when I first added it, but now when you pull up the update page it only shows the date that's in the table.
In Oracle, a default on a column means that if a record is inserted into the table without mentioning that field, then use the default. My guess is that since the field is displayed on your page, you are writing NULL or spaces to it, so it is definitely included in the insert statement.
So you need to either take it off the page, add an update trigger, or even better, write a process in Apex to update it whenever the record is modified -- perhaps an After-Submit computation.