Home > Forum > Forms > Datatable and datarow in an archived element

Datatable and datarow in an archived element
0

Hi,

When instances are "live", datatables / datarows are just nice objects to use. However, when an element is archived, datatable shows "No data preview for an archived element", while datarow does not render at all.

Scenario: a parent and 1+ children. You can have a datatable in the parent's form to show the list of children along with some relevant info, and each child may have a datarow to show the same about the parent. While parent & children are not archived, everything is just fine, but when you archive any of these elements, datatable/row gets empty and datatable shows that "No data preview ... archived ...".

Data sources are custom T-SQL, but I suppose that's not the problem.

I need to show the data within datatable / datarow no matter the element status.

Thank you,
Mihail

MVP

Hi Mihail,
Archiving moves data to different tables/databases, and removes them from the main WFElements, WFElementDetails tables as far as i am aware.
If your custom queries try to get data from those, there just simply isn't any data to get, as those are moved to archive database (assuming you are archiving by moving to archive db).

This could result with datarow not rendering, although for datatables it seems like Webcon explicitly turned that preview off (we're not yet using arch. functionalities, so didn't had a chance to check it).

In reply to: Maksymilian Stachowiak

Hi Mihail,
Archiving moves data to different tables/databases, and removes them from the main WFElements, WFElementDetails tables as far as i am aware.
If your custom queries try to get data from those, there just simply isn't any data to get, as those are moved to archive database (assuming you are archiving by moving to archive db).

This could result with datarow not rendering, although for datatables it seems like Webcon explicitly turned that preview off (we're not yet using arch. functionalities, so didn't had a chance to check it).

Indeed, the straight forward query would return nothing, but at least you have the chance to work on it and solve whatever problems arise once data is archived. We solved the last problem - SQL vs archived elements, then we've got stuck with Webcon control not doing anything. Seriously annoying. To overcome this we have to think to an additional item list to throw at it with the last combination of children just before archiving the parent-children structure.