- Log in to post comments
User bio
404 bio not found
Member since Sep 2, 2016
Posts:
Replies:
I looked into this a little more, and discussed it with a colleague. My understanding at this point is:
- Not all field types support HTML parsing/conversion
- For fields that do support HTML conversion, there should be properties called Convert HTML Tag (which should be set to true if you want to parse <br/> tags) and Ignore HTML Tag (which should be set to false) in the Text Format section of the field's properties in the Inspector pane
If you're still having trouble with this, please feel free to open a support case in IService so that TrakCare support can take a look at your report with you.
- Log in to post comments
Hi Steven,
I started to take a look at this but haven't found an answer. There is documentation here that suggests Logi Report does support parsing and rendering HTML tags, but I'm not sure why it is inconsistent in your case. Is there some additional formatting in the values for ARCIM_Desc or MRDIA_ICDCode_DR that is causing Logi Report to parse HTML tags in one but not the other?
- Log in to post comments
Open Exchange applications:
Certifications & Credly badges:
Sam has no Certifications & Credly badges yet.
Followers:
Sam has no followers yet.
Following:
Sam has not followed anybody yet.
Thank you, Evgeny and Tim (and DC AI Bot)! That does seem to work. It's been long enough that I'm not totally sure anymore, but I think at some point I looked at that readme, saw the first bullet point that says, "To retain the old behavior where %IPM routines and classes mapped across all namespaces, run
zpm "enable -map -globally"", and thought that was all I needed - now I see that "as well IPM repository settings" is the key difference in the description ofzpm "enable -community".