I want to create a field that will tell me,
if that field's content is empty (ex: no attachment),
it will reflect in another field that it is empty.
For that reason,
I have created/tested a Rich-Text field in a form.
Let's say that Rich-Text Name is Test1.
Then, I added a computed text field, let's say the name is Test2.
In Test2 field, I set the formula as this,
#If(Test1!="";"Yes";"No")
As a result, in the Test2's field, it does not show me that the Test1's field is empty, even though it has no text/attachment inside the Test1 field.
I have tested many times, and the result is still the same.
Please help me on this matter to solve this problem.
Thank you in advance.
There is no direct solution AFAIK. If using LotusScript is an option for you, here's a common workaround to find out whether an RT field is empty:
Put the focus on the RT field by calling NotesUiDocument.GoToField("Test1").
Select all contents of the RT field by calling NotesUiDocument.SelectAll().
The call to NotesUiDocument.SelectAll will raise an error (can't remember wich error code) if the RT field is empty. Trap that error using On Error GoTo <label of error handler>. If the code does not enter the error handler, you know the RT field is not empty. If it does, you know the RT field is empty. You can then take the appropriate action, e.g. put a message in text field 'Test2'.
To make this approach more user-friendly, I'd also suggest you add some code that puts the focus back on the original field (i.e., the field that had the focus before the above LS code was triggered).
Related
I am using Version 11.1.2fp2 IBM Cognos. I have many simple case statements that do not validate. The Report Runs. The report produces the expected output of data.
The error is RSV-VAL-0034 Failed to validate the variable 01. CRX-API-0016 The expression input string is empty: """".
CASE
WHEN [Grant Agency TRACCD FRGBIL FOBTEXT with Budgets].[REAUTH_SDE_LAWS] IS MISSING
THEN ''
ELSE TRIM([Grant Agency TRACCD FRGBIL FOBTEXT with Budgets].[reauth_law_chapter])
END
Kindly, I have attached a screen shot with the Do you have any insights?
The CRX error family is usually linked to variable or report expressions, which means it's probably not tied to the data item case statement. Given the report runs it may also indicate the report expression is not actually used anywhere.
Please have a look at: https://www.ibm.com/support/pages/crx-api-0016-report-upgrade
The "Validate" button in the Data Item Expression dialog doesn't validate that expression. It validates the entire report. It is often misleading because the message displayed may have nothing to do with the expression you are looking at.
Here's what to do.
Close the Data Item Expression dialog.
Click on the More button in the top right (the 3 dots arranged vertically).
Select Validate report.
Select the first item in the Validation response.
Click Select.
If Cognos chooses to be nice to you, it will navigate to and highlight the offending object.
#dougp mentioned, an unprocessable variable from cognos is just what happened. Sometimes it might get hard to find the variable itself. One way of finding it is to get the xml definition and the search for the the declared variable.
Reimporting the report won’t overwrite until you choose the saving location.
The root cause is the variable "Boolean1" was never used by the report. The variable "Boolean1" was not tied to the data item in the case statement. I created the variable "Boolean1" and forgot about it. I did not use the variable "Boolean1" in the report. I found the variable "Boolean1" and removed it. Now my validation of the report expressions works fine. I value your insights.
Seeking for guidance, in Maximo 7.6 the change status dialog box has a field (toemailaddr) Label: Notification E-mail for work Order change status. See the picture below.
What I am seeking guidance on is how do I edit that field to where I make it to default blank over populating the user logged in e-mail by default? Is this even possible?
I have looked in the change status dialog on WOTRACK as well extracted Library.XML and did not find a way to change from it filling in by default with users e-mail to just remaining blank.
I apologize in advance if it shows to be tagged incorrectly.
Picture of what I am looking to change to show blank
It's the Maximo "psdi.app.workorder.virtual.WOChangeStatus" MBO class that is defaulting that value in.
If the presentation-level default values run after the MBO add() code, then a simple presentation "Default Value" control should allow you to override that.
If that doesn't work then you can try an automation script. It would need to be against the WOCHANGESTATUS object and on the "add" action. If that runs after the Java code then you could grab that field (toEmailAddr) and set it back to an empty string. I assume the screen would still update with that change.
I have not looked at the code for any downstream effects clearing this field might have. It could be that Maximo is coded to always send out that email and if the email address is empty it would likely error at that point.
create an automation script named WOCHANGESTATUS.NEW
(automation scripts that are named after a mbo followed by .NEW are executed when a new instance of a MBO is created, they can be used to initialize column values. )
put a single line in the script.
mbo.setValueNull("TOEMAILADDR")
mark script active and save it
I have the following two lines of code:
Set customerView = db.GetView ("(Lookup - Customers by Reference)")
Call customerView.refresh()
Very occasionally, the 2nd line will give users an Error 4000, Query is not understandable
Restarting Notes gets rid of it, but it sometimes comes back for a couple of users.
This has only recently started happening, and I've not made any changes to the view.
EDIT
To explain further, nowhere in the function that is throwing the error is there any code relating to a FT Search, which makes me think that this may be an error that IBM have stuffed up in R9.0.1
Check Forms and Fields (especialy fields!) you use in search formula of the view.
Maybe you search text value in non-text fields.
Fields are shared between forms, i.e field is unique not within form, field is unique within NSF. So, first time you create field - NSF writes it's properties (field type included) in NSF structure. And if you have two forms containing field with same name, but with different types (text and non-text) - you'll get this error.
I saw this error several times, and every time it was caused by FT-queries or search formulas what tries to search some text value in field, that initialy was created as non-text (date or numbers field).
If this is the case... Well, it's hard to get rid of this error. Basically you'll have to delete this field from every form and every document in nsf, then compact it using copy-style, then recreate field in right type and restore it's values in docs using right type - it helps usually.
I am trying to do something simple in Tibco Spotfire, to try and set a document property in webplayer by specifying a property in the url. I cannot get this to work.
I have created a document property called 'test' which is simply a string
I have then created an input text control bound to that document property
I would expect that if I opened that report in webplayer with a url prepended with &configurationBlock=test%3D"helloworld" then the input text would be populated with the value helloworld. However, it is not.
This seems to be a reasonably simple thing to get working, I have tried what I think is every possible variant of encoding the data to no effect. Is there something I am doing wrong that could make this work.
you are going to hate this answer :)
you need to put a semicolon at the end of the parameter assignment. so you should have:
http://example.com/Spotfire/stuff?configurationBlock=test=helloworld;
I want to check if the field values in the "Issues" field is null or not using a groovy script as a validator. As there are certain scenarios that will require the user to fill in this field, however not always so I cannot make it just a required field.
So it would be the latter field "Issue" is what I want to see if it is null. And to be able to check the status of "Link Issue".
EDIT: This gave me the appropriate solution for the issue at hand. https://answers.atlassian.com/questions/14203790/how-to-set-linked-issues-as-mandatory-field-on-issue-creation