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 have a report that includes a bit data type field from a SQL Server 2012 database whose values are either 0 or 1. For some reason the 1 values are read as -1.
I'm able to suppress the minus sign, but that only changes how the field is displayed. Any values of 1 are still read as -1.
The following is the default description of the field in the masterfile:
The documentation (Describing Data With WebFOCUS Language 8.08) says that binary integers may be specified as one of the following: I1, I2, I4, I8. It also notes the USAGE must be either P or D. I've tried both with no luck.
Also, I'm not sure why the documentation specifies that for ACTUAL to USAGE conversions ACTUAL integer is only automatically converted to either USAGE integer or date when it also says to set the USAGE for binary integers to either P or D.This message has been edited. Last edited by: <Emily McAllister>,
I've got the same thing going on here. I would be most interested in hearing how this plays out. For now, when I need to test the field, I test for NE 0 instead of EQ 1 or EQ -1.
I have also noticed this same error. After looking at the masterfile and seeing to error, I just decided to check for -1 instead of 1. I would also be interested in the outcome if you open a case.
Thank you everyone for the suggestions. I've used some of these workarounds in the past, so that wasn't the issue. I was just trying to figure out why this problem was occurring in the first place.
I'll try to open a case since it seems like I'm not the only one who has seen this. I think for the time being, I'll use defines in the master file itself so the data appears as it is in the database.