David Watkins

Adding the `qualifier_kind` and `qualifier_id` cols to the `grid_col_def` table looks like it should be okay. However due to the nature of the unique index on the col def table...

Some sample grid data: ``` INSERT INTO report_grid_column_definition (report_grid_id, position, column_entity_kind, column_entity_id, display_name, column_usage_kind, rating_rollup_rule, entity_field_reference_id, column_qualifier_kind, column_qualifier_id) VALUES (:gridId, 1, 'APP_GROUP', 5, null, 'NONE', 'NONE', null, null, null); INSERT...

Sample data query: ``` with required as ( select * from ( values (1, 'APPLICATION', 79, 'MEASURABLE_CATEGORY', 1), (2, 'APPLICATION', 79, 'LOGICAL_DATA_FLOW', null), (3, 'APPLICATION', 79, 'PHYSICAL_FLOW', null), (1, 'APPLICATION',...

Alternative without the need for creating `DSL.row(...)` entries: ``` with required as ( select rgcd.id col_id, 'APPLICATION' ref_k, age.application_id ref_i, rgcd.column_qualifier_kind att_k, rgcd.column_qualifier_id att_i from report_grid_column_definition rgcd cross join application_group_entry...

API Tested with: ``` ### report grid tabular extractor POST http://localhost:8000/data-extract/report-grid/external-id/5a4845aa-7fae-425f-92be-b52caafa78e9?format=XLSX Content-Type: application/json { "entityReference": {"kind": "ORG_UNIT", "id": 10}, "scope": "CHILDREN" } ### report grid tabular extractor POST http://localhost:8000/data-extract/report-grid/external-id/5a4845aa-7fae-425f-92be-b52caafa78e9?format=JSON Content-Type:...


Maybe 4 fields ?: - OU name - OU id - Parent Ext Id - Parent Waltz Id

@JWoodland-Scott, please double check for CI's.

**Topics:** - Recent [1.41 release](https://github.com/finos/waltz/releases/tag/1.41) - Improved calendar view - On demand mesurable attestations (i.e. Functional Taxonomy mappings) - Actor improvements - Survey predicates based on app characteristics (e.g. in-house...

Hello ! (Dave + Jess)