As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
We are using an Oracle database, meaning all of our date fields are considered datetime (HYYMDS) --> For the most part, our time-portions are actually 00:00:00, so I would like to hide them as easy as possible.
The solution I had in mind was the following: USAGE=HYYMD, ACTUAL=HYYMDS --> but this results in FOC1647
Is there any way to keep the time portion, but not show it in reports (not using a define)?
Note: the reason I don't want to end up with YYMD format is to avoid compatibility issues between YYMD fields and HYYMDS fields in my business viewThis message has been edited. Last edited by: Peter,
Prod: WebFOCUS 8.0.06 on Win2008/Tomcat7/LDAP Mode Test: WebFOCUS 8.0.06 on Win2008/Tomcat7/LDAP Mode
You can change their definition in the master as follows:
..., USAGE=YYMD, ACTUAL=DATE, $
That way they will be handled as "just dates" in the WebFOCUS layer.
If you have cases where the same field needs to be handled as Date-only under some circumstances and DateTime under others (hey, it's possible ), then you can define 2 different FIELDNAME's on the very same database one (ALIAS) as follows:
That way, you can use "MY_DTTM" when DateTime calls for it, and "MY_DATE_ONLY" when only the Date piece is required. No DEFINES or date transformation expressions needed!
I was hoping to be able to keep all my fields in the same format (DateTime) to prevent them being incompatible in InfoAssist. (comparing Date fields to DateTime fields requires formulas which I want to avoid for IA-users when possible)
But from what I understand it's not possible in such a way. (Strange as you can put a HYYMDS value in a HYYMD field within InfoAssist...)
Thanks for the help!
Prod: WebFOCUS 8.0.06 on Win2008/Tomcat7/LDAP Mode Test: WebFOCUS 8.0.06 on Win2008/Tomcat7/LDAP Mode