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.
I get this error: FOC2590 - AGGREGATION NOT DONE FOR THE FOLLOWING REASON: FOC2565 - THE OBJECT OF BY/ACROSS CANNOT BE CONVERTED TO SQL FOC2566 - DEFINE DOS CANNOT BE CONVERTED TO SQL FOC2567 - FUNCTION HCNVRT CANNOT BE CONVERTED TO SQL
yeilds this: FOC2590 - AGGREGATION NOT DONE FOR THE FOLLOWING REASON: FOC2565 - THE OBJECT OF BY/ACROSS CANNOT BE CONVERTED TO SQL FOC2566 - DEFINE PRINT_DATE CANNOT BE CONVERTED TO SQL FOC2584 - CANNOT IMPLICITLY CONVERT VALUE OF FIELD SERVICE_DATE TO USAGE HMDYY
DEFINE FILE PB_TRANSACTION_CHARGES_VW LOCATIONGROUP/A10=IF J3.POS_VW.FACILITY_TYPE__CODE EQ 11 THEN 'OFFICE' ELSE 'OTHER'; PRINT_DATE/HMDYY=PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.SERVICE_DATE; END TABLE FILE PB_TRANSACTION_CHARGES_VW SUM PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.PROCEDURE_QUANTITY AS 'Units' PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.RVU_WORK AS 'wRVUs' BY LOWEST PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.PERIOD_OF_POST_DATE BY LOWEST J1.PROVIDER_VW.SUI BY LOWEST J1.PROVIDER_VW.PROVIDER_NAME BY LOWEST J3.POS_VW.LOCATIONGROUP BY LOWEST J2.BILL_AREA_VW.BILL_AREA_NUM AS 'CC' BY LOWEST PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.PATIENT_NAME BY LOWEST PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.SERVICE_DATE BY LOWEST J0.CPT_CODE_VW.CPT_CODE AS 'Cpt' BY LOWEST J0.CPT_CODE_VW.CPT_NAME AS 'Cpt Name' WHERE
DEFINE FILE PB_TRANSACTION_CHARGES_VW
LOCATIONGROUP/A10 = IF J3.POS_VW.FACILITY_TYPE__CODE EQ 11 THEN 'OFFICE' ELSE 'OTHER';
END
-*
TABLE FILE PB_TRANSACTION_CHARGES_VW
SUM
PB_TRANSACTION_CHARGES_VW.SERVICE_DATE/HMDYY
PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.PROCEDURE_QUANTITY AS 'Units'
PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.RVU_WORK AS 'wRVUs'
BY LOWEST PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.PERIOD_OF_POST_DATE
BY LOWEST J1.PROVIDER_VW.SUI
BY LOWEST J1.PROVIDER_VW.PROVIDER_NAME
BY LOWEST LOCATIONGROUP
BY LOWEST J2.BILL_AREA_VW.BILL_AREA_NUM AS 'CC'
BY LOWEST PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.PATIENT_NAME
BY LOWEST PB_TRANSACTION_CHARGES_VW.PB_TRANSACTION_CHARGES_VW.SERVICE_DATE
BY LOWEST J0.CPT_CODE_VW.CPT_CODE AS 'Cpt'
BY LOWEST J0.CPT_CODE_VW.CPT_NAME AS 'Cpt Name'
WHERE...
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
Waz, What do I change in the master file? Usage? Under Usage, Type? I tried changing that from HYYMDs to YYMD. The fex then throws the type mismatch error.
This master file is against a view that was set up for us...not sure if that is factoring in...
Maybe the HDATE thing will work...I wish I could just right click the field in the GUI and pick the format I want...
Note that the ALIAS MUST always relate the actual column name in the RDBMS. If you want an internal date format then the ACTUAL needs to be changed to DATE with the USAGE reflecting the format that you want used in your report.
This normally converts to SQL just fine.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
We have a field called service_date. It prints like this:
2015/04/26 00:00:00.000
...not very appealing. We'd prefer 04/26/2014.
I just saw this post and even though it's closed, I'll add my 2 cents worth.
Although the empty timestamp is obviously redundant the date format IMHO is the only one worth considering and using.
1) It is the only format where dates will sort automatically even in alphanumerc format
2) There is no confusion about what is the month or the day
3) It is the internationally accepted SI format.
Here in Canada things are moving at a glacial pace towards acceptance of the SI format (blank cheques issued by all the banks require the date to be entered in SI format, for example). Some businesses uses DD/MM/YYYY and others (mostly American subsidiaries) use MM/DD/YYYY. Of all the different formats MM/DD/YYYY is the least defensible as far as I'm concerned.