How to explore object members dynamically using .NET Core | LINQ Reporting Engine

When loading from json data source objects of the same structure are not assignable to each other.

This is especially painful when trying to reuse templates if there are multiple of the same data types that are not in a list. The types cannot be stored in a variable to be then built be the nested type. Would it be possible to add an option to either allow similar json types to be assignable in the var. OR add an option to the doc tag to allow building relative to a specific object? For instance working like contextual object member access? This would solve this issue and allow for more concise templates. (21.2 KB)


We have added a new feature request as WORDSNET-21109 in our issue tracking system to use variables in nested document using LINQ Reporting. You will be notified via this forum thread once this feature is available. We apologize for your inconvenience.

Hi @tahir.manzoor,

The feature request was just a suggestion, there is an actual bug here where the same json data cannot be assigned to a variable since it is being treated as different.

Please mark this as a bug, I should not have lumped the feature request into the bug report.


Thanks for your inquiry. We will investigate this issue and update the issue tracking system accordingly. Moreover, we will inform you via this forum thread once there is an update available on it.


JSON format itself does not provide any type information for complex objects, so it is impossible to determine whether two objects are of the same type or not. Deciding by field names of an object is not a panacea. Consider the following example.

{ “pet”: { “name”: “Smokey” }, “owner”: { “name”: “Peter Adams” } }

Should pet and owner be considered as instances of the same type, because they have the same field name ? Obviously, no. Although for some other objects, the answer to the same question could be “yes”, there is no way to indicate this using JSON notation itself. (The only exception is for array items representing complex objects). So actually, this is a limitation of JSON format rather than a bug of LINQ Reporting Engine.

We can support your scenario only after working with dynamic data sources that is missing feature. The issue IDs are WORDSNET-16421, WORDSNET-16017, and WORDSNET-12148. We apologize for your inconvenience.