| MS-24317 |
Blocker |
SharePoint folders should appear in ReportMagic Files and Schedules should run |
Fixed and issue that meant SharePoint folders were not appearing in Files and any associated report schedules would give a system error. |
| MS-23896 |
Blocker |
[ReportMagic.xxx:] / [MagicSuite.xxx:] macros should use the MagicSuite macro default not the ReportMagic macro default |
When using [MagicSuite.xxx:] or [ReportMagic.xxx:] macros with a macro default connection (rather than an explicit connectionName= parameter), the macro will now correctly pick up the MagicSuite connection default. Previously, macros would fail with a missing connection error on Tenants that had only configured a MagicSuite macro default, requiring a workaround of specifying the Connection name explicitly on every macro. |
| MS-23975 |
Blocker |
Magic Suite Framework: Logging in using firefox should work |
Firefox users will no longer experience a login loop when signing into any MagicSuite App. |
| MS-24127 |
Blocker |
[LogicMonitor.UserList:] macro should not generate Json serialization macro error (4.3 fix) |
Fixed an issue where the [LogicMonitor.UserList:] macro was broken due to changes in the LogicMonitor API. |
| MS-24106 |
Blocker |
Opening files from ReportMagic files system should open correctly first time |
Opening Ncalc files from ReportMagic files system now outputs the correct value in Ncalc101 without needing to edit the file first |
| MS-24007 |
Critical |
[MagicSuite.ReportJobCount / List:] macros should not fail with a system error |
Fixed a performance issue in count macros where counting items (like Report Jobs) was unnecessarily slow. Count operations now use an optimized API endpoint that returns the count directly, rather than fetching all the data first. This makes count macros significantly faster, especially when counting large numbers of items. Users will notice faster execution of macros that count items, such as [MagicSuite.ReportJobCount] and similar counting operations throughout the application. |
| MS-24257 |
Major |
[Web.Html:], [Web.Text:] and [Web.Table:] macros should give better / more readable errors in specific scenarios |
Error messages shown when a Web macro fails to fetch a page are now clearer and more descriptive, making it easier to understand what went wrong. |
| MS-24155 |
Major |
ReportMagic: Schedules: Create - should not have two "Is Managed" fields |
The create dialog for ReportMagic Schedules now does not have two "Is Managed" fields |
| MS-24288 |
Major |
Huge macro messages should not cause browser to hang when raising feedback |
Huge macro messages no longer cause the browser to hang when raising feedback. |
| MS-24113 |
Major |
Docs: [Meraki.OrganizationAdminsList:] examples should be updated so that they do not error |
Fixed the [Meraki.OrganizationAdminsList:] macro examples so they do not error. |
| MS-24062 |
Major |
NCalc Library Functions: files should be updated to allow them to work/be run successfully |
Library .ncalc files in the Function Folder now do not error when run/used |
| MS-24063 |
Major |
NCalc Library Tutorial: files should be updated to allow them to work/be run successfully |
Library .ncalc files in the Tutorial Folder now do not error when run/used |
| MS-24254 |
Major |
Edit in NCalc 101 button should not be disabled in read only folders |
The "Edit in NCalc101" button and context menu options are now available for .ncalc files even when they are in read-only folders, allowing you to open and work with the file in NCalc101 regardless of the folder's write permissions. |
| MS-24117 |
Major |
Help: [MagicSuite.ConnectionList:] and [MagicSuite.ConnectionProperty:] macros should have an extra help example |
Added an additional help example to the [MagicSuite.ConnectionList:] macro and the [MagicSuite.ConnectionProperty:] macro. |
| MS-23705 |
Major |
[LogicMonitor.Graph:] macro's xValueType should not be listed (not applicable) |
The xValueType parameter is now not listed in the help for this macro, as it is not relevant. |
| MS-23704 |
Major |
[Jira.Graph:] macro's xValueType should affect the xAxis not be listed (not applicable) |
The xValueType parameter is now not listed in the help for this macro, as it is not relevant. |
| MS-23701 |
Major |
[AlertMagic.MetricsGraph:] macro's xValueType parameter should not be listed (not applicable) |
The xValueType parameter is now not listed in the help for this macro, as it is not relevant. |
| MS-23898 |
Major |
Schedules: Regular Users & Tenant Admin users should be able to clone a Schedule which has "IsManaged=True" or "MaxConcurrentReportJobs" set |
Fixed an issue where PDL-managed Schedules (or Schedules with a max concurrent report job set > 1) could not be cloned by users without Super Admin rights. |
| MS-15087 |
Major |
PowerPoint: PPTX tables should be able to hold ForEach/Continue/Break/If etc without giving system error |
Fixed an issue where using the [ForEach:] (and related macros such as Continue, Break, etc) would not work properly when used inside a table cell in PowerPoint. |
| MS-24004 |
Major |
The RMScript help section "In RMScript or in the template?" should be clarified |
The RMScript help page has been updated to clarify when to use RMScript files versus the template, fix a contradictory statement about positioning output macros, and correct the description of how RMScript files are processed when called. |
| MS-15462 |
Major |
Files: the Edit File menu option should be greyed out when a file is selected |
Edit Files is now not present as an option when: a. right clicking in the files view with no file selected, and b. in the files tool bar with no file selected
|
| MS-15359 |
Major |
New File/New Folder buttons should not be usable in read only folders within a read only file system |
New File/New Folder buttons now are not usable in read only folders within a read only file system |
| MS-24304 |
Major |
[LogicMonitor.UserList:] macro should not fail |
Fixed an issue where the [LogicMonitor.UserList:] macro was broken due to changes in the LogicMonitor API. |
| MS-24131 |
Major |
Raw exception messages must not appear in the Batch Job Message (as shown on the Progress Page and elsewhere) |
Error messages shown on the batch job progress page are now clear and readable. Previously, technical details and stack traces could appear in the message - these are now shown only in the application logs, while the progress page displays a concise, plain-language description of what went wrong. |
| MS-24299 |
Major |
[DateTime:] Late-evaluation variable references fail when using Calculate Shorthand assignment for 5 out of 6 add* parameters |
Fixed late-evaluation variable references ({=Variable}) not working with DateTime add* parameters in Calculate Shorthand assignments. |
| MS-24320 |
Major |
ReportMagic: File actions must not appear in read-only GitHub subfolders |
Read-only GitHub-connected folders now correctly show the lock icon and hide file management options at all folder levels, not just the top level. |
| MS-24405 |
Major |
The [Meraki.EndOfLife:] macro should produce accurate results |
Meraki End of Life information is now accurate using the [Meraki.EndOfLife:] macro. Previously some product names and regions could appear garbled. The macro now obtains each affected product correctly, including its individual model numbers and the regions it applies to. |
| MS-24446 |
Major |
[MagicSuite.xxxProperty:] macros should include the Connection name in the error message upon failure |
When various [MagicSuite.xxxProperty:] macros (such as [MagicSuite.ConnectionProperty:] fail, for example due to a connection that doesn't have the correct access, the error message is now more helpful and tells you which MagicSuite Connection was used. |
| MS-23702 |
Major |
[Table.Graph:] macro's xValueType should affect the xAxis |
When explicitly set, the xValueType parameter is applied (the default is Auto as before). |
| MS-23703 |
Major |
[Database.Graph:] macro's xValueType should affect the xAxis |
When explicitly set, the xValueType parameter is applied (the default is Auto as before). |
| MS-24355 |
Major |
[LogicMonitor.SummaryValue:] aggregations=MaxDateTime and precision=High should not always be the startDate |
Fixed an issue with the [LogicMonitor.SummaryValue:] macro, where the earliest/latest date and time for a value (MinDateTime and MaxDateTime) could be reported incorrectly - often showing the start of the reporting period - when using high precision. These date and times are now reported accurately. |
| MS-24323 |
Minor |
Files: When replacing a file back into the folder it was in, "copy" should not be put at the end of the title |
Dragging a file into the folder it's already in no longer renames it with "copy" added to the title. |
| MS-23996 |
Minor |
Files: Video player should have a back/exit button |
When viewing a video file in Files, a Back button is now shown above the player so you can quickly return to the folder you came from - no need to use the browser's back button or navigate manually. Additionally, WebM video files now show the correct video icon alongside other video formats such as MP4. |
| MS-24220 |
Trivial |
Files: Video player should in keep with Dark Mode theme |
The video player in the Files area now correctly uses dark mode colours, removing the white bars that appeared around the player when using a dark theme. |
| MS-23880 |
Trivial |
ReportMagic landing page uses incorrect vendor casing for Salesforce |
Corrected "SalesForce" to "Salesforce" on ReportMagic landing page. |
| MS-24453 |
Trivial |
[HubSpot.Query:] macro help example should not have a missing trailing square bracket |
Corrected the [HubSpot.Query:] macro example which was missing a trailing closing square brakcet. |