Missing fields in v2.0 about wiprint HOT 5 CLOSED

Of the multiple issues I just entered, this is the only one that is currently a show stopper for me. FYI.

from wiprint.

I think I know what the problem is. I'm only doing simple parsing for dates and dropping things if they look close enough to an invalid date because TFS stores some "empty" date fields as 1/1/9999 and I didn't want that junk to make it through to printing. Numbers or strings that contain numbers can be loosely parsed as dates (through the wonders of JavaScript) and my script is dropping them as junk.

I just looked through the API and I can add another call to check the field type before choosing how to display it. Hopefully it won't add much overhead to rendering the pages.

In the meantime I will ease up on the date restrictions. I pushed v2.0.1 as a workaround while I work on better field parsing. It's now in the marketplace. Thanks for the feedback.

from wiprint.

2.0.1 seems to display all the missing fields. It does feel quite a bit slower than 2.0 did. Thanks!

from wiprint.

Good to know it's displaying better. Let me know if anything else displays wrong or strangely.

from wiprint.

Closing this as this specific bug was fixed.

from wiprint.