We imported our data into Spectrum using the SDX, and continue to use the SDX for import. There is a serious inconsistency with your SDX information and what actually happens in the data base. Why you would not use Boolean types in your data is beyond me.
If you check a box for true, it adds a Y in the field, if you uncheck the box it makes the field Null, not N.
Some Examples in IM_ITEM_MASTER_MC.
Mix_Flag Checked Y Not Checked - Empty
In your SDX document you state the following
|
AD |
Mix_Flag |
Auto-create Mix? |
Text |
1 |
(Y)es or (N)o only. |
All our imported items show N if not a mix, all added items that are not a mix show Empty, when I write formulas looking for N I have run into miscalculations that we just found out because If Mix_Flag = 'N' evaluates to false (except for the items we imported following your instructions.
This is the same for Taxable_Flag, Use_Tax_Flag, Commission_Flag. This is for one table only!!
|
AA |
Taxable_Flag |
Subject to Sales Tax? |
Text |
1 |
(Y)es or (N)o only. |
|
AB |
Use_Tax_Flag |
Subject to Use Tax? |
Text |
1 |
(Y)es or (N)o only. |
|
AC |
Commission_Flag |
Commissions? |
Text |
1 |
(Y)es or (N)o only. |
Discontinue_Flag
SDX states:
|
AE |
Status_Discontinue_Flag |
Status |
Text |
1 |
(A)ctive, (D)iscontinued or (N)ot used. Defaults to Active if blank. |
So it should be A, D, or N, but in reality if Active - N, Discontinued - Y, Not Used - X
Now I need to view all my Crystal Report files and see if I checked for the N as opposed to Not 'Y'.
You need to fix your data and instructions on how it is brought in. You are inconsistent with your data, and again, why not use Boolean for the Y/N check box items instead of a String of 1. It would make more sense, allow programing to be done easier and there would be no inconsistencies. Only use a String of 1 for multi-option data, but make sure it matches your documentation.
If you stick with a String of 1, make the unchecked box be N, if you are going to be consistent then all NO's (unchecked boxes) being empty then make all of them empty, not some N and some Empty.
Maybe they don't teach consistency in the Universities any longer for coding, but your company should demand it to help the rest of us that write code consistent and write instructions for what should actually be in the fields not Y and Empty
Les Papp
| Company | Cardi Corp |
| Job Title / Role | IT / Programing |
| I need it... | Yesterday...Come on already |
Dear Viewpoint Suggestion Box contributor;
We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs.
Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.
© 2023 Trimble Inc. All Rights Reserved. Viewpoint®, Vista™, Spectrum®, ProContractor™, Jobpac Connect™, Viewpoint Team™, Viewpoint Analytics™, Viewpoint Field View™, Viewpoint Estimating™, Viewpoint For Projects™, Viewpoint HR Management™, Viewpoint Field Management™, Viewpoint Financial Controls™, Vista Field Service™, Spectrum Service Tech™, ViewpointOne™, ProjectSight® and Trimble Construction One™ are trademarks or registered trademarks of Trimble Inc. or its affiliates in the United States and other countries. Other names and brands may be claimed as the property of others.
This isn't something we are going to modify or address in the near term. We are going to focus our energies on higher vote enhancements for now.
Understand, I'm not asking you to change your data tables, I know that wouldn'thsppen, but you should at least make your documentation match what is in your tables and what is expected based on how the code works, that could at least help us who code or use Crystal Reports.
Les Papp II
Dude - I'm just saying what it is. Needless to say we aren't going to rewrite the entire system just for folks that create reports.
Again, the A/P tables were created in 1981...HR tables were new in 1999 etc. We had different programmers in different eras and no one thought about anyone who'd want to write a report back then. Another factor is what PRO-IV (the business logic) requires.
I am not trying to argue with you...rather I was just attempting to say we understand your request. I just hope you understand where we are coming from.
Boolean existed 30 years ago, I was there. Just bad programming. I started programming in 1979 and used boolean.
But the real problem is your documentation doesn't support your programming logic. Everything should be consistent from one table to the next. You should have standards when you code tables. Regardless of you logic, the opposite of Yes (Y) is not "", it is No (N) even per your SDX documentation, whoever wrote that understands logic.
If No is "" you need to document that and it should be the same for ALL your tables. And your tables & your SDX manuals need to match. You need to fix this.
Les Papp II
Appreciate the feedback. Understand that Spectrum has been developed over 30 years and these things under the hood are very common.
One of the benefits of using the same business logic over the years was that it did not require that we rewrite our code every time the logic changed. One of the downsides is that things were written in the style at the time. We spent 5 years getting the front end consistent with version 14.
Thanks for writing in!
Geoff