You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The obsidian dynamic data block renders HTML returned in a SQL query as TEXT instead of rendering the HTML. The only choices under "Column Configuration", in the column field types, are Text, Boolean, Currency, Date, Date Time, Number and Person. There needs to be an HTML option and the block needs to render the HTML the same way the original block used to when we couldn't designate the column field types.
I created this page on the demo site containing an example of using the regular dynamic data entry block and how the buttons appear correctly. It that same query is used in a version that contains the obsidian dynamic data block, you'll see that the buttons are just rendered as html text.
NOTE: I had to check the box indicating that I was able to reproduce the issue on a fresh install or on the demo site. I was only able to reproduce on a fresh install because the demo site does not currently have the obsidian dynamic data block available.
Actual Behavior
SQL Query returns HTML that gets rendered as text instead of as HTML. (i.e. when wanting to include a button in the resulting rows)
Expected Behavior
The block would render the HTML the same way the old block did.
Steps to Reproduce
Add both the Obsidian Dynamic Data block and the original Dynamic Data blocks to a page.
Create a SQL query that returns data including at least one column as HTML that would be for a button to appear in that column.
Put that query in both blocks in the SQL Query block setting
You will see that the Obsidian block just has the text value of the HTML where the old block will actually have a functioning button in that column.
Example query:
SELECT Id, CONCAT(p.FirstName, ' ', p.LastName) as PersonName
, '<a class="btn" href="/Person/' + CAST(p.[Id] AS NVARCHAR(MAX)) + '/contributions" target="_blank" rel="noopener noreferrer"><i class="fas fa-money-bill-alt"></i></a>' AS [ContributionsTab]
, '<a class="btn" href="/Person/' + CAST(p.[Id] AS NVARCHAR(MAX)) + '/extendedattributes" target="_blank" rel="noopener noreferrer"><i class="fas fa-info"></i></a>' AS [ExtendedAttributesTab]
FROM Person p
Issue Confirmation
Perform a search on the Github Issues to see if your bug or enhancement is already reported.
Reproduced the problem on a fresh install or on the demo site.
Rock Version
16.6
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered:
@treusch Hi Tina - I am happy to share that an HTML column type has been added to the Dynamic Data obsidian block and will be available in v17 with this commit.
Description
The obsidian dynamic data block renders HTML returned in a SQL query as TEXT instead of rendering the HTML. The only choices under "Column Configuration", in the column field types, are Text, Boolean, Currency, Date, Date Time, Number and Person. There needs to be an HTML option and the block needs to render the HTML the same way the original block used to when we couldn't designate the column field types.
I created this page on the demo site containing an example of using the regular dynamic data entry block and how the buttons appear correctly. It that same query is used in a version that contains the obsidian dynamic data block, you'll see that the buttons are just rendered as html text.
NOTE: I had to check the box indicating that I was able to reproduce the issue on a fresh install or on the demo site. I was only able to reproduce on a fresh install because the demo site does not currently have the obsidian dynamic data block available.
Actual Behavior
SQL Query returns HTML that gets rendered as text instead of as HTML. (i.e. when wanting to include a button in the resulting rows)
Expected Behavior
The block would render the HTML the same way the old block did.
Steps to Reproduce
Example query:
Issue Confirmation
Rock Version
16.6
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: