Hi JWT007,
Are you seeing this behavior on standard ItemTypes? If so, could you specify which one(s), so I can take a look at this in a more current version to see if this is still present?
Chris
Hi Christopher, thanks for the quick response.
Unfortunately (if I am not mistaken) the only OOTB FormattedText property in the Aras InnovatorSolutions database is on the "Help" ItemType - which is empty by default.
So while I am sure I could fudge some broken data :) I am not sure that would prove anything.
In our customer project we have some item types that rely heavily on the FormattedText fields - but all in custom item-types.
I see. I set up a custom ItemType with a formatted text property then and tested this in a local 12.0 SP4 instance. While I'm not seeing anything unexpected, I'm also testing it with relatively simple data.
Are you able to elaborate on how the formatted text field is being used and what kind of data you're trying to retrieve? Are you trying to access a list of values stored inside of an HTML table for instance?
Chris
Nothing special some fields have a bold header .. few are more than a few lines long.
Here an example (have to obfuscate a bit to not get in trouble with the customer :P)
To be implemented by FOO BAR team for FOO-XYZ (ref. ABC_CFG_001-PTF Configuration management throught MMI).
To be implemented by FOO L2 team for FOO-AAA.
FOO-AAA is not operational yet and not handed over to OPS, but must be kept aligned to FOO-XYZ.
In the database is the following:
<html> <head></head> <body > <span lang="EN-GB" style="mso-ansi-language:EN-GB">To be implemented by <span style="mso-spacerun:yes"> </span>FOO BAR team for FOO-XYZ (ref. ABC_CFG_001-PTF Configuration management throught MMI).<br />To be implemented by FOO L2 team for FOO-AAA.<br />FOO-AAA is not operational yet and not handed over to OPS, but must be kept aligned to FOO-XYZ. <o:p></o:p></span></body> </html>
In this case, the problem is the undefined namespace prefix 'o' ("<o:p></o:p>")
