WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question
Home > Forum > Latest posts

latest posts

In reply to: Damian Kryński

Hi,

I hope they will fix this "bug" anyway -> the action using the additional database connection is executed outside the transaction -> so it does not use the data changed during the action. To use the data, it must be previously saved in the database -> so the CTE action must be executed on subsequent steps.

I believe there won’t be any changes to this functionality.
According to the help documentation in WEBCON BPS Designer Studio, such queries are not supported due to the way they are wrapped.
Additionally, the official online documentation confirms that the WITH syntax is not supported:
https://docs.webcon.com/docs/2025R2/Studio/ConnectionsAndDataSource/DataSources/DataSource_MSSQL#12-sql-query

It appears that the fact it worked previously was more of a feature, and in future versions, even potential workarounds may no longer be effective.

In reply to: Maksymilian Stachowiak

Glad it's solved, I won't add a ticket then, semicolons are statement terminators in SQL so the behavior seems logical with that added to the context.
Error message isn't pretty, and explaining unfortunately.

Hi,

I hope they will fix this "bug" anyway -> the action using the additional database connection is executed outside the transaction -> so it does not use the data changed during the action. To use the data, it must be previously saved in the database -> so the CTE action must be executed on subsequent steps.

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).

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

In reply to: Adrian Motyka

Assuming you don't need to fetch data from the current transaction, as a workaround that doesn't require major changes (like changing the data source to a connection at each point of use), I suggest changing the connection in your data source configuration from "current BPS database" to a new connection to the same database. Then the data source won't hook into the transaction and the error won't occur.

Hi,

Thanks for the reply.

Your method works for an action performed on a path, -> but the data source won't hook into the transaction, so it is not possible to work on data in a transaction -> action needs to be moved to next steps where Data Base data is updated -> so it is not good in some scenarios.

UPDATE:
I've already figured out why CTE didn't work on Data Table -> in earlier versions of Webcon semicolon before

;With T1 as
(Select ISNULL(Old,'') as Old, pivotcolumn1
from WFHistoryElements...

It was ok in 2025.2.1.42 - in 2025.2.1.91 it throws an error :)

Privacy overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.


To see a full list of the cookies we use and learn more about their purposes, visit our Privacy Policy.