Close popover
Jeremy Becker (jpbecker)
Wells Fargo N.A.
Software Architect
Wells Fargo N.A.
jpbecker Member since 2005 29 posts
Wells Fargo N.A.
Posted: March 8, 2017
Last activity: March 22, 2017

TrueFalse property optimized as a varchar(5)

Why does the default optimization on my setup produce a varchar(5) when I optimize the TrueFalse property? Shouldn't this be a BOOLEAN?

I noted a problem after optimizing that a report written to filter based on this property's "IsFalse" condition was raising an exception. At first, I believed it to be a data type mismatch but upon restarting the system everything shook out - even though the TF property exists in a database column as a varchar(5). I realize there's probably some "Pega-plumbing" going on to resolve this issue, but does anyone know if this is always the case with optimization of TF properties and why?

***Updated by moderator: Lochan to update Categories; add SR Exists group tag***

Data Integration Reporting User Experience Support Case Exists
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.