Error when generating document from model document

[Geert Bellekens]

Details:
When generating a document from a virtual document on which I dragged a package, results in numerous error messages popping up, saying:
ADODB.Fields [0x800a0cc1]

Item cannot be found in the collection corresponding to the requested name or ordinal.

DBerror contains:

07/02/2023 10:20:53
ADODB.Fields [0x800a0cc1]

Item cannot be found in the collection corresponding to the requested name or ordinal.

Context:
select t_object.* FROM ((t_object LEFT JOIN t_diagramobjects ON t_object.Object_ID = t_diagramobjects.Object_ID) LEFT JOIN t_object t_object_1 ON t_object.Classifier = t_object_1.Object_ID) INNER JOIN t_package ON t_package.Package_ID = t_object.Package_ID where t_object.Object_Type='Package' and ( ( t_object.PDATA1 IN ('35019') ) )
GetLongVal( "Instance_ID" )

The same thing goes perfectly fine on a .qea file, but not on an SQL Server model


Steps to Reproduce:
- Create a package, with a diagram
- Add two classes, and association and a few attributes to those classes
- Create a new package, with a diagram, and a «model document» element
- drag the first package onto the model document
- select the default model report as template
- Press F8 and generate the model

Tested in version 16.1.1624

Reported

Geert

[Modesto Vega]

Hi Geert,

You have and ( ( t_object.PDATA1 IN ('35019') ) ) in the join. Are you sure the value of 35019 is not giving you a headache? Is it the same on both repos?

[Geert Bellekens]

Hi Geert,

You have and ( ( t_object.PDATA1 IN ('35019') ) ) in the join. Are you sure the value of 35019 is not giving you a headache? Is it the same on both repos?

35019 is an ObjectID, so it's not going to be the same in both repo's.

I ran an integrity check, but still the same. Weirdly I didn't have this problem when I tested on another test machine (with another database), but with the same version.
Anyhow, I hope Sparx will react to my bug report and give me a clue of what is going wrong here.

Geert

[steen.jensen]

Got  error with version 16.1.1624, its a bug, had it reported last week.
Have to revert to 16.1.22 to get it working with Modell document as earlier versions.