SharePoint 
Confluence 
Case Studies 
Reports
Why are columns not clickable in the Prolaborate Report Widget?
For a report column (typically the artifact name) to be clickable and link to its detailed view, you must use specific aliases in your SQL query:
- Use ‘name’ as the alias for the object name column.
- Use ‘classguid’ as the alias for the ea_guid column.
If different aliases are used, Prolaborate cannot identify the clickable fields, and links will not be generated.
Example Query:
SELECT
o.ea_guid AS classguid,
o.Object_Type AS basetype,
o.Name AS name
FROM t_object o
WHERE o.Name LIKE 'EBL%'
Why is the ea_guid column not displaying correctly in the report widget?
Prolaborate hides the ea_guid column unless its alias is set to ‘classguid’. Without this specific alias, the GUID will not be recognized or rendered in the report output.
Example Query:
SELECT
o.ea_guid AS classguid,
o.Status,
o.Name
FROM t_object o
WHERE o.Name LIKE 'EBL%'
How can I display icons in the Report Widget?
To enable icons for elements in your report, ensure you include:
- ‘Object_Type’ with the alias ‘basetype’
- ‘Stereotype’ with the alias ‘stereotype’
To keep the icons functional without showing the columns, you can prefix them with hide_.
Example Query:
SELECT
o.ea_guid AS classguid,
o.Object_Type AS hide_basetype,
o.Stereotype AS hide_stereotype,
o.Name
FROM t_object o
WHERE o.Name LIKE 'EBL%'
Column aliases containing uppercase letters and underscores (e.g., HTML_Description) can cause rendering issues. Instead, use lowercase aliases with underscores or simplified naming conventions.
Example Query:
SELECT
o.ea_guid AS classguid,
o.Note AS html_description,
o.Status
FROM t_object o
WHERE o.Name LIKE 'EBL%'
Why do I see an “Invalid or Column Name Not Found” error when saving a report widget, even if the preview works?
This error often occurs when the “MDG Based Report” option is enabled while using a custom SQL query in a Prolaborate report widget.
To resolve this:
- Go to the widget’s configuration settings.
- Disable the “MDG Based Report” option.
The “MDG Based Report” setting is intended for reports that rely on forms defined in a Modeling Language. When working with custom queries, enabling the option can cause column mismatches during save, even if the preview works correctly. Disabling this ensures the widget saves and displays custom query results as expected.
How can I customize the fields displayed in Prolaborate report widgets?
You can customize the fields shown in report widgets using three approaches, depending on your use case:
For Specific Element Types (Stereotypes)
- Navigate to Modeling Language > [Your Language] > Default Profile.
- Locate the relevant stereotype.
- Drag and drop the desired fields into the sections.
Note:
- These fields will be visible in report widgets only when filtered by that stereotype.
For General Fields (Without Filtering by Stereotype)
To set default fields for all elements regardless of stereotype:
- In Modeling Language, go to General Properties (top-right corner).
- Click the Elements.
- Add the desired fields under the Basic Attributes section.
Note:
- These will appear in widgets that do not filter by stereotype.
Using Custom SQL Queries
For full control over which fields are shown:
- Use a custom SQL query within the report widget.
- Ensure the “MDG Based Report” option is disabled.
- Manually define the fields you want to retrieve and display.
Note:
- Always verify that your column aliases (e.g., name, classguid) match Prolaborate’s expected values to ensure proper rendering and linking.
