[BLOSSOM-56] Blossom data type dialog does not work properly with hierarchical data types Created: 20/Dec/11  Updated: 06/Dec/14  Resolved: 23/Jan/12

Status: Closed
Project: Blossom
Component/s: data-extension
Affects Version/s: 1.2.3
Fix Version/s: Data Extension 1.0.1

Type: Bug Priority: Blocker
Reporter: Tomas Brimor Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot-1.png     PNG File Screenshot.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When creating hierarchical data types that should use blossom data type dialogs (one specific dialog for each type) all data types in the hierarchy get the same dialog.

The blossom dialogs are accessible by manually entering the URL to the dialog so blossom has created them properly (I assume) but fails to connect the right dialog to the correct data type.

Attached images clarifies the setup for reproducing.



 Comments   
Comment by Danilo Ghirardelli [ 21/Dec/11 ]

Could this be related to MGNLDATA-127 ?

Comment by Erik Alphenaar [ 16/Jan/12 ]

With 1.0.1 the correct dialog is shown, but when saving the contents of a dialog in the hierarchy, the validation of the specific dialog is not called. Instead the validation method of the top dialog type is called.

In the above example: the validation of SupportGuidesDialog is called when saving a SupportGuideSection.

Comment by Tobias Mattsson [ 23/Jan/12 ]

@Erik, I can't reproduce the problem you describe. Please open a new issue with instructions on how to provoke the error if the problem remains.

Comment by Jan Haderka [ 06/Dec/14 ]

Bulk close of old resolved issues.

Generated at Sun Feb 11 23:29:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.