I'm confused now. You originally said "Need to print this Field2 value in a report. Thought of working out with a nested report". That doesn't sound like a requirement to me, it sounds like a design you came up with that doesn't satisfy the actual requirement. To me, it sounds like the requirement is to display both field 1 and field 2, and be able to print field 2 which is a json string. You don't say if the json string is a bunch of columns and values, or maybe an array of columns/values that you would like formatted by column. The solution will depend on whether you have multiple rows of field 1, and if the json can have multiple rows. Also not sure if you are displaying just the json string in field 2 or you want it formatted to display columns. If you want an all-in-one solution that allows you to display and print fields 1 and 2, you need to build a datawindow that has field 1 and all columns from field 2 and populate it manually. If you just want to print field 2 formatted, then take the json from the selected row, put it into a datastore and print the datastore.



Don't confuse requirements with design. Requirements will say "I need to see these fields on this page: x,y,z. I need to be able to add new xyz, update yz, and delete a row, etc". Requirements do NOT say "put a nested datawindow inside datawindow 1 in the top right corner". Letting users decide where data goes is fine, but don't let them tell you that you have to use a nested datawindow.

Sorry if I'm confusing. Something that assumed that others know. When I told that Field2 is jsonb field, entered in a tabular dw, I assumed that other could understand that there may be more than one row and more than one column.



When I tried the suggested solution, to put two dw's in a composite and then finally in a freeform, I'm not satisfied with the outcome. The data are not at the proper place to make the report better.



May be the place, 'top right corner', might have shown my interest, but one could understand that difference exists in nested as well as composite report's outcome.



Since I could not achieve the desired result, I came up with some more details. That's all.

LOL! A tabular dw can have 1 or more rows, so multiple rows is an important piece of info. Either way, I gave you a solution that will work. If you don't want to use it, that's up to you. You should consider being more polite to people that are trying to help you instead of trying to make them sound dumb by saying you assumed someone could understand. People are more likely to help when you are polite. I'm done on this one, good luck.

The place where need to display the data is not possible with composite DW. We need to display the data at top right end corner, which is not possible with composite dw.