How to suppress extra data from all PiWeb reports?

[[Te...]]

I am working on a guide and will attach when it is finished it should work with 2017. I have nothing at 17 at the moment to test it with though.

[[Te...]]

I am going to load 2017 on a PC and create the .ptx it will be good practice for me before I finish of the guide. I will attach it as soon as I am done.

[[Te...]]

Here is the 2017 version again place the .ptx file to:

C:\Users\Public\Documents\Zeiss\CALYPSO\protocol\PiWebReportingTemplates

it should show up in the Generic Template section.

Than all you have to do is selected it as the Printout you want to use

Modified Additional Results 2017.zip

[[Ri...]]

Thank you Ted Hurlbutt for your help, it is very much appreciated!

[[Mi...]]

Did we find out why the filtering method (GX, GG, etc...) was removed? First time I have seen that on the report.

Kinda like it as it will stop people from asking me how I filtered the ID/OD's

Thanks

[[Te...]]

They were removed from my original because I used a template that was created in Calypso 2017 on Calypso 2018.

I am making a guide on how I created it because it looks like it might have to be created with every new version of Calypso.

The first .ptx I made using Calypso 2018 has the GG, GX stuff and then I made another .ptx using Calypso 2017 for users that have not upgraded.

The earlier one is 2018 and newer one is 2017.

[[Mi...]]

Ok................

Sounds Good

[[Te...]]

Found a minor flaw in the modified report the text box that covers the bar graphic is not big enough and you will get exceed data to show up. I am going to fix both the 2017 and 2018 .ptx files and also attach the guide on how I created it as soon as the guide is finished. The guide is mostly done, need to make this corrected and then finish proof reading and "prettying" it up. My co-worker is going to use the guide to create the .ptx so after he does that it should be good to go.

[[Ri...]]

This really needs to be handled by Zeiss.

If you are using PiWeb SBS or Enterprise this isn't a problem as it isn't a characteristic that is put into the database, but for whatever reason on the PiWeb Reporting Plus side of things it is being added as a characteristic (for whatever reason), so the report is setup to show all characteristics.

Has anyone reached out to software support to see if they are aware of customers being upset about not being able to turn this on/off?

I think it should be an option added into Calypso to make this a toggle.

[[Mi...]]

SO I am messing around with the conditions and I have hit a snag. As you can see in the pic, I have 2 GG's that are on top of each other. Where did the larger (GG) come from? Its early and I am probably missing something..

Thanks

[[Te...]]

What report are you using?

Looks like there is a text file and a icon in the same location.

I should be posting my guide early next week have it almost finished, on the last proof read.

[[Te...]]

Here is the guide with a notepad of all the strings ($). I think I got rid of all the typos please feel free to let me know if I did not. I also have attached the corrected .ptx files for 2017 and 2018.

If someone follows the guide and has an issue I would be curious to what the issue is so I can add it to the guide if needed.

Thanks,
Ted

Strings for Modifing Additional Printout.txtPTX FOR CALYPSO 2018.zipPTX FOR CALYPSO 2017.zipModifying Additional Position Result in the PiWeb Report.pdf

[[Mi...]]

Please sign in to view this quote.

I am using the table protocol. If I have a text file in there I cant seem to track it down

[[Te...]]

You might have to make the Background white it is set to transparent that is why you might be seeing both. Try that and see how that works.

[[Mi...]]

I did that just now. Same thing. Im not sure what I am doing wrong. You would think its simple to do.

Throw in text box, add the ${Qdb.Property("ISOevalType")} in the text box, then over to properties and add in the cond formatting.

Am I doing that correct?

[[Te...]]

Try changing the font to transparent at the top.

[[Mi...]]

Yeah tried that also. Guess its just not in the cards for this to work on my table protocol LOL. 🙄

Ill keep at it. 🤣

[[Te...]]

You are really close, un-check font in the in the conditions and change the main font to transparent and you should be good.

Text and graphic covered.JPGno text just graphic.JPGFont transparent.JPGCondition Box.JPGCondition Box.JPG

[[Mi...]]

Yupp. Changing the Condition font did the trick. Whew what a PIA lol

Least now its solved 😃 😃 😃 😃 😃

[[Je...]]

Hello All,

I think I may have figured out another solution. When you go into PiWeb and you bring up the report that has the (M) result you can delete this line. Step 1 shows you where to click step 2 you expand the today tree and double click the root part line. Step 3 Then you can see all your values with (M) when you select them the x will turn red so you can delete them. Step 4 hit the refresh button and then you can save as a pdf.

[[Te...]]

Cool thanks for sharing. Would this have to be done in every program since you are deleting the (M) lines?

[[Je...]]

Unfortunately it seems that way. You have to run your program then edit each result in piweb.

[[Br...]]

so would you just put - {^((?!\.\(L\)).)*$} into the filter to remove the LMC lines?

[[Te...]]

maybe does it do (L) for LMC?

[[Ri...]]

Calypso 2016

Please sign in to view this quote.

This appears to suppress M and L, but only in the PiWeb Designer.

{^((?!\.\(M\)).((?!\.\(L\))))*$}

I managed to see this work one time for a report.
Once I closed (after saving) it no longer suppresses the "L" result on reports.