| MS-21121 |
Blocker |
The [Database.List:] macro should work as expected |
Fixed an issue where the 'includeHeaderRow' parameter was incorrectly looking for 'includeHealth', which then had a knock-on effect to alter the macro's core functionality. |
| MS-20967 |
Blocker |
New Tenant / User signing in via Magic Suite should be able to accept terms of service |
Fixed an issue where it was not possible for Tenant Admins to accept the Terms of Service. |
| MS-20769 |
Blocker |
[LogicMonitor.Dashboard:] macros should not be broken |
Fixed broken [LogicMonitor.Dashboard:] macros, after a change by LogicMonitor to the way dashboards are structured. |
| MS-21078 |
Critical |
[Jira.IssueList:], [Jira.Table:], [Jira.TimeInState:] and [Jira.Graph:] should return results. |
Fixed an issue where various Jira macros were not returning results. |
| MS-21062 |
Critical |
Release Notes should be accessible via the Docs App and in ReportMagic help |
Fixed an issue where no release notes were shown in the Docs app and in ReportMagic help. |
| MS-21014 |
Critical |
[Toggl.ProjectProperty:] should not time out / system error so frequently |
Fixed an issue where [Toggl.xxx:] macros may time out, after receiving rate limit message from the Toggl API. |
| MS-20987 |
Critical |
All Monaco editors in cancel dialogs should be coloured correctly in Dark Mode |
Various Monaco Editors are now coloured correctly in Dark Mode when cancelling out of the dialog |
| MS-20939 |
Critical |
ReportMagic/DataMagic Meraki Connections: including any json config should not render the connection invalid in a Meraki Connection - 3.25 only |
Fixed an issue where Meraki Connections that have configuration would be shown as invalid in the Connections pages. |
| MS-16193 |
Major |
Powerpoint and Word - the [Shape.Format] macro with picture fill should use image aspect ratio unless both or no dimensions are specified |
The [Shape.Format:] macro now uses the image aspect ratio to calculate width / height, if only heightCm or widthCm is specified. |
| MS-20994 |
Major |
[xxx.Image:] macros should work in Word headers and footers |
[xxx.Image:] and [xxx.Graph:] macros now work in Word input documents, when placed in headers and footers. |
| MS-20938 |
Major |
ReportMagic/DataMagic Meraki Connections: including invalid json config in a Meraki connection should show an invalid connection consistently across builds |
Meraki Connections now show as an invalid connection consistently when including invalid json config |
| MS-20911 |
Major |
[Logicmonitor.Dashboard:] hyperlink should point to desired dashboard (3.25) |
Fixed an issue where the [LogicMonitor.Dashboard:] macro would attempt to set the wrong dashboard URL when used in conjunction with the insertHyperlink=true parameter. |
| MS-20890 |
Major |
Help: [ReportMagic.ApplyBrand:] macro should mention what aspects of Word are affected |
Updated the help for the [ReportMagic.ApplyBrand:] macro to describe what each parameter does. |
| MS-20844 |
Major |
[LogicMonitor.ThresholdsReport:] should be removed from everywhere as it no longer supported |
Removed the [LogicMonitor.ThresholdsReport:] macro from showing up in the help as it already states it's not supported. |
| MS-20692 |
Major |
ReportMagic: the Create button should be disabled on the DataMagic Syncs page for on a Tenant that has no LogicMonitor Connections |
The Create button is now disabled on the ReportMagic DataMagic Syncs page if the Tenant has no LogicMonitor Connections. This is now consistent behaviour with the same functionality in the Admin app. |
| MS-21096 |
Minor |
For the ReportMagic macro help (in Docs app and in ReportMagic help), the "Type" of several parameters in the macro parameters table should be correctly shown |
Fixed an issue where several macro parameters did not show the 'Type' correctly in the macro help parameter tables |
| MS-21087 |
Minor |
Help: "Viewing Statistics about a Connection" section should also now mention Git/Github connection |
Updated the help about viewing Connection statistics. |
| MS-20954 |
Minor |
Powerpoint [Xxx.Image:] macros for line alt text should produce a macro error when the line is not fully horizontal or vertical |
Fixed an issue with [XXX.Image:] macros that align images with PowerPoint lines, where a non-compliant (not fully horizontal / vertical) line would not be recognised as containing a macro and just fail silently / do nothing. |
| MS-20912 |
Minor |
Help: [LogicMonitor.DeviceDataSourceList:] Example 1 & 2 should not have rogue characters |
Fixed an issue where the [LogicMonitor.DeviceDataSourceList:] macro help examples contained spurious characters that stopped them running. |
| MS-20883 |
Minor |
[ReportMagic.ApplyBrand:] macro error should not show an incorrect macro name |
Fixed an incorrect error message related to the [ReportMagic.ApplyBrand:] macro when used for a document that isn't Word or PDF. |
| MS-20815 |
Minor |
Help: [LogicMonitor.EventSourceGroupList:] remove example 2 as this uses the property parameter which is not used by this macro |
Removed irrelevant example for the [LogicMonitor.EventSourceGroupList:] macro. |
| MS-21094 |
Trivial |
[Highlight.xxx:] macro icons in the help tree / docs should be correct (and not the 'ban' icon) |
[Highlight:] macro icons now show the 'info' icon rather than the 'ban' icon. |
| MS-20957 |
Trivial |
Help Typo: [ReportMagic.ApplyBrand:] macro parameters table (properties row) should have a closing bracket |
Tiny formatting error has been fixed in the parameter table of the [ReportMagic.ApplyBrand:] macro |
| MS-20920 |
Trivial |
Help: [LogicMonitor.DeviceConfigSourceList:] Example 2 should not have rogue characters |
Updated the [LogicMonitor.DeviceConfigSourceList:] macro to remove spurious characters in the second help example. |
| MS-20913 |
Trivial |
Help: [ReportMagic.ReportScheduleProperty:] Examples 1 - 6 should be tagged as Normal mode only |
The examples 1-6 for the [ReportMagic.ReportScheduleProperty:] macro are now tagged as normal mode only. |
| MS-20902 |
Trivial |
Help: [ReportMagic.ReportJobList:] example 2 and 3 should have mode=normal specified in some places to mean it consistantly runs regardless of mode |
Added the parameter/value "mode=normal" into various normal mode only macro help examples, to ensure they always runs in normal mode, even if in legacy mode e.g. in report studio. |
| MS-20899 |
Trivial |
Help: [LogicMonitor.Dashboard:] an extra example should be added which can be run by any customer |
Added an additional example to the [LogicMonitor.Dashboard:] macro, that can be run by any customer. |
| MS-20853 |
Trivial |
Help: [LogicMonitor.InstanceAnalysis:] all examples should be able to be run by any customer |
Updated the [LogicMonitor.InstanceAnalysis:] macro help examples so they can be run by any customer just by inserting the examples. |
| MS-20852 |
Trivial |
Help: [LogicMonitor.AlertAnalysis:] all examples should be able to be run by any customer |
Updated [LogicMonitor.AlertAnalysis:] macro help examples. |
| MS-20851 |
Trivial |
Help: [LogicMonitor.WidgetStatus:] all examples should be able to be run by any customer |
Updated the help examples for the [LogicMonitor.WidgetStatus:] macro. |
| MS-20850 |
Trivial |
Help: [LogicMonitor.WebsiteProperty:] all examples should be able to be run by any customer |
Updated the help example for the [LogicMonitor.WebsiteProperty:] macro. |
| MS-20831 |
Trivial |
Help: [LogicMonitor.PaymentInformation:] all examples should use cardExpMonth/AccountBillingEmail not a incorrect value |
Updated the help examples for the [LogicMonitor.PaymentInformation:] macro. |
| MS-20818 |
Trivial |
Help: [LogicMonitor.FinancialInformation:] all examples should be able to be run by any customer |
Updated the help examples for the [LogicMonitor.FinancialInformation:] macro. |
| MS-20816 |
Trivial |
Help: [LogicMonitor.EventSourceList:] all examples should be able to be run by any customer |
Updated the help example for the [LogicMonitor.EventSourceList:] macro. |
| MS-20808 |
Trivial |
Help: [LogicMonitor.DeviceGroupProperty:] all examples should be able to be run by any customer |
Updated the help examples for the [LogicMonitor.DeviceGroupProperty:] macro. |
| MS-20803 |
Trivial |
Help: [LogicMonitor.DeviceDataSourceProperty:] example should be able to be run by any customer |
Updated the help example for the [LogicMonitor.DeviceDataSourceProperty:] macro. |
| MS-20802 |
Trivial |
Help: [LogicMonitor.DeviceDataSourceList:] examples should be able to be run by any customer |
Updated the help examples for the [LogicMonitor.DeviceDataSourceList:] macro. |
| MS-20801 |
Trivial |
Help: [LogicMonitor.DeviceCount:] example 2 should be able to be run by any customer |
Updated the help example for the [LogicMonitor.DeviceCount:] macro. |
| MS-20800 |
Trivial |
Help: [LogicMonitor.DeviceConfigSourceProperty:] example should be able to be run by any customer |
Updated the help example for the [LogicMonitor.DeviceConfigSourceProperty:] macro. |
| MS-20799 |
Trivial |
Help: [LogicMonitor.DeviceConfigSourceList:] examples should be able to be run by any customer |
Updated the help examples for the [LogicMonitorl.DeviceConfigSourceList:] macro. |
| MS-20794 |
Trivial |
Help: [LogicMonitor.DataSourceList:] example should be able to be run by any customer |
Updated the help example for the [LogicMonitor.DataSourceList:] macro. |
| MS-20781 |
Trivial |
Help: [LogicMonitor.CollectorProperty:] example 3 and 4 should be able to be run by any customer |
Updated the help examples for the [LogicMonitor.CollectorProperty:] macro. |
| MS-20779 |
Trivial |
Help: [LogicMonitor.AppliesToFunctionProperty:] example should be able to be run by any customer |
Updated the help example for the [LogicMonitor.AppliesToFunctionProperty:] macro. |
| MS-20778 |
Trivial |
Help: [LogicMonitor.AppliesToFunctionList:] example 3 should be able to be run by any customer |
Updated the third help example for the [LogicMonitor.AppliesToFunctionList:] macro. |
| MS-20777 |
Trivial |
Help: [LogicMonitor.AlertTable:] example 2 should be able to be run by any customer |
Updated the help example for the [LogicMonitor.AlertTable:] macro. |
| MS-20776 |
Trivial |
Help: [LogicMonitor.AlertStatus:] the example should be able to be run by any customer |
Updated the help example for the [LogicMonitor.AlertStatus:] macro. |
| MS-20774 |
Trivial |
Help: [LogicMonitor.AlertMap:] Examples should be able to be run by any customer |
Updated the help examples for the [LogicMonitor.AlertMap:] macro. |
| MS-20772 |
Trivial |
Help: [LogicMonitor.AlertCount:] Examples should be able to be run by any customer |
Updated the [LogicMonitor.AlertCount:] macro help examples. |
| MS-20768 |
Trivial |
Help: [ReportMagic.ReportScheduleProperty:] Examples should be able to be run by any customer |
Updated help examples for the [ReportMagic.ReportScheduleProperty:] macro. |
| MS-20767 |
Trivial |
Help: [ReportMagic.ReportScheduleList:] Examples should be able to be run by any customer upon load into Report Studio |
Added a better help example to [ReportMagic.ReportScheduleList:] macro. |
| MS-20765 |
Trivial |
Help: [ReportMagic.ReportJobProperty:] Examples should be able to be run by any customer |
Updated the help examples for the [ReportMagic.ReportJobPRoperty:] macro. |
| MS-20764 |
Trivial |
Help: [ReportMagic.ReportJobList:] Examples should be able to be run by any customer upon |
Updated help examples for [ReportMagic.ReportJobList:] macro. |
| MS-20763 |
Trivial |
Help: [ReportMagic.ReportConnectionSummary:] Example should be able to be run by any customer |
Updated the help example for the [ReportMagic.ReportConnectionSummary:] macro. |
| MS-20761 |
Trivial |
Help: [ReportMagic.ReportBatchJobProperty:] Examples should be able to be run by any customer |
Updated help examples for the [ReportBatchJobProperty:] macro. |
| MS-20760 |
Trivial |
Help: [ReportMagic.ReportBatchJobList:] Examples should be able to be run by any customer |
Updated the help examples for [ReportBatchJobList:] macro. |
| MS-20759 |
Trivial |
Help: [ReportMagic.ReportBatchJobCount:] Example should be able to be run by any customer upon load into Report Studio |
Improved the help example for the [ReportMagic.ReportBatchJobCount:] macro. It also no longer requires a ReportMagic Connection. Added the ScheduleName parameter. The properties parameter is no longer required (as it is irrelevant). |
| MS-20758 |
Trivial |
Help: [ReportMagic.FeedbackProperty:] Examples should be able to be run by any customer upon load into Report Studio |
Improved the help examples for the [ReportMagic.FeedbackProperty:] macro. |
| MS-20757 |
Trivial |
Help: [ReportMagic.ConnectionStatusProperty:] Example should be able to be run by any customer upon load into Report Studio |
Updated the help example for the [ReportMagic.ConnectionStatusProperty:] macro. |
| MS-20756 |
Trivial |
Help: [ReportMagic.ConnectionProperty:] Example 2 should be able to be run by any customer |
Updated the help example for the [ReportMagic.ConnectionProperty:] macro. |
| MS-20754 |
Trivial |
Help: [Toggl.WorkspaceProperty:] example should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.WorkspaceProperty:] macro help example now runs out of the box without using hard-coded IDs. |
| MS-20753 |
Trivial |
Help: [Toggl.UserProperty:] examples should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.UserProperty:] macro help examples now work out of the box without hard-coded IDs. |
| MS-20752 |
Trivial |
Help: [Toggl.UserList:] example should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.UserList:] help example now works out of the box without using hard-coded values. |
| MS-20751 |
Trivial |
Help: [Toggl.TimeEntryProperty:] example should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.TimeEntryProperty:] macro help example now works out of the box without hard-coded IDs. |
| MS-20750 |
Trivial |
Help: [Toggl.TimeEntryList:] example should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.TimeEntryList:] macro help example can now be run out of the box without hard-coded values. |
| MS-20749 |
Trivial |
Help: [Toggl.ProjectReportProperty:] example should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.ReportProperty:] macro help example now runs out of the box without using hard-coded IDs. |
| MS-20748 |
Trivial |
Help: [Toggl.ProjectProperty:] example should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.ProjectProperty:] macro help example now runs out of the box without hard-coded IDs. |
| MS-20747 |
Trivial |
Help: [Toggl.ProjectList:] examples should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.ProjectList:] help examples now all run out of the box without hard-coded values. |
| MS-20746 |
Trivial |
Help: [Toggl.ClientProperty:] example should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.ClientProperty:] macro help example now runs properly when inserting the default example without using hard-coded workspace IDs. |
| MS-20745 |
Trivial |
Help: [Toggl.ClientList:] examples should not use our Ids, and should be able to be run by any customer upon load into Report Studio |
The [Toggl.ClientList:] macro help examples now run properly using customer IDs instead of using hard-coded values. |
| MS-20744 |
Trivial |
Help: [Table.Save:] all 5 examples should have a table present before the macro. |
Added tables to all the help examples for the [Table.Save:] macro. |
| MS-20743 |
Trivial |
Help: [Table.RowCount:] example 2 should have a table present before the macro |
Added a table to the second help example for the [Table.RowCount:] macro. |
| MS-20742 |
Trivial |
Help: [Table.MergeCells:] example should have a table present before the macro |
Added a table to the [Table.MergeCells:] macro help example. |
| MS-20741 |
Trivial |
Help: [Table.Graph:] all 5 examples should have a table present before the macro |
Added tables to the [Table.Graph:] macro help examples. |
| MS-20740 |
Trivial |
Help: [Table.Format:] in all 5 examples there should have a table present before the macro |
Added tables into all help examples for the [Table.Format:] macro. |
| MS-20739 |
Trivial |
Help: [Table.Delete:] example 1 should have a table present before the macro |
Added a table into the example for the [Table.Delete:] macro. |
| MS-20738 |
Trivial |
Help: [Table.ColumnCount:] example 1 should have a table present before the macro |
Added a table into the first example for the [List.ColumnCount:] macro. |
| MS-20737 |
Trivial |
Help: [Table.WorldMap:] example 2 should have a table present before the macro |
Added a table in example 2 for the [Table.WorldMap:] macro. |