MDG document generation with ImageRef tagged value type

[Luigi2021]

Hi,

I have created an MDG Class which has a tagged value type as one of its attributes. The tagged value type is defined as:

Code: [Select]

Type=ImageRef;All works fine except that when I want to generate a document the following text is shown:

Code: [Select]

id=1948243495;mdg=Global;name=RiskMatrix.PNG;type=Bitmap;instead of the image. Which is of course not what I want.

When I create a ImageRef tagged value type and add it “manually” to an element and generate the report it works fine.

Any suggestion how I can solve this?

Thanks in advance!

[Paolo F Cantoni]

Hi,

I have created an MDG Class that has a tagged value type as one of its attributes. The tagged value type is defined as:

Code: [Select]

Type=ImageRef;All works fine except that when I want to generate a document the following text is shown:

Code: [Select]

id=1948243495;mdg=Global;name=RiskMatrix.PNG;type=Bitmap;instead of the image. Which is of course not what I want.

When I create an ImageRef tagged value type and add it “manually” to an element and generate the report it works fine.

Any suggestion on how I can solve this?

Thanks in advance!

Ciao, Luigi!

I have previously posted that the addition of tagged values from an MDG is self-inconsistent.  Sometimes the profile is added <profile>::tag_name and other times just tag_name is added.  I would investigate what gets added to the t_objectproperties table in the different modes you are using.  That may help to determine which form "works" for the generation.  You can then adjust the automated version to achieve the same result.


HTH,
Paolo

[Luigi2021]

Ciao Paolo,

I compared the MDG tagged value with the non MDG tagged value in the t_objectproperties table but I don't see any differences. As far as I understand there is no difference once a record is inserted in the t_objectproperties table. How it came there MDG or manual shouldn't matter execpt if the property is prefixed or something. Or am I wrong about this?


I don't get it

[qwerty]

Since this is related to the document generation you should probably report a bug. I seem to remember having had trouble with the imageref too, though in another context (don't recall the details).

Generally a TV is recognized to belong to a profile by its GUID which holds encrypted information. If the profile is not present for som ereason you might get the weirdness Paolo is talking about. Probably nothing you need to care about.

q.