Something as simple as what table does what. The current documentation is nothing but a listing of the tables and field. Any half decent programmer can get this with free tools from the internet. Many things are not obvious by reading the table structure. The data surgeons in tech support have some of this already. Maybe a public wiki or some collaborative effort between report writers would help.
The JobBOSS Data Dictionary for version 12.0 is now published and can be found in the customer portal under the JobBOSS Utilities and References Download section (Document: 27.240.736).
Not Very clear on where to actually find this it took me a little while. Its actually in the Knowledge Base then Utility and Other then Utilities and its like the fourth doc down. Here is a link to it to save some people some time.
https://customers.exact.com/docs/DocBinBlob.aspx?Download=1&ID=%7bbc92a4a1-bdb2-4afb-8bd5-950ffc9b8253%7d&AttID=%7bcaadb1cb-6b04-408e-97ed-ce7b6127b812%7d&Version=
Where is this document??? How do you access the customer portal?
Maybe I'm an idiot, but I cannot find this document. I search for the document number and exact times out before I get a response. I cannot even find "JobBOSS Utilities and References Dowload" section. I find the download section, with utilities under that, but 27.240.736 is not listed. Can somebody give me step by step instructions as to where this document is please??
I agree, i often spend more time finding together how the data is stored than writing the actual SQL Query to collect the data.
Things like the material and material description coming from different tables based on on Source.Source_Type for example.
Referring to this:
( CASE
WHEN Source.Source_Type = 1 THEN Material_Req.Material
ELSE Source.Material
END) AS 'Part Number'
,
( CASE
WHEN Source.Source_Type = 1 THEN Material_Req.Description
WHEN Source.Source_Type = 3 THEN Material.Description
ELSE Source.Description
END) AS 'Description'
(I was able to fill my report with 2 and 3 choices, while there are far more types...)
No, i didn't figure this out, it required Mr Poland to hint where the data is when, once he replied to my email, the code was easy.
Documenting this would save us as much time as them explaining the same things multiple times to different people.
Agreed. it's frustrating to have spent so much time making custom reports and still be fairly lost when looking for links. A simple listing of relations would make creating custom reports easier and faster. And no special coding or bug checks would be required!!