Ver. 2024.2 - SharePoint Canvas, logging, MIP, word shape links

New in version 2024.2:

  • Extended MIP error log (target: get better understanding if permissions are not sufficient)
  • Extended support for changes of hyperlinks behind shapes in Word documents (for example, inserted image which is having link behind)
  • Extended logging options when adding new SharePoint site
  • Improved processing of SharePoint Canvas pages containing links with :
  • Added that per default when backup option is selected (only local or network drive locations), only backup of changed documents is created

Ver. 2024.1.1 - Microsoft.Information.Protection update

New in version 2024.1.1 (minor upgrade):

- Updated Microsoft.information.Protection (MIP) components

Recommended update if you use MIP

Ver. 2024.1 - Improvements in command line, SharePoint Summary Links....

New in version 2024.1 (recommended upgrade)

  • Default configuration changed to include developer logs
  • Extended log to highlight if developer log is enabled
  • Fixed bug that replacements in Summary Links web part were not saved
  • Extended ReplaceMagic to support Unicode characters in case of changes in document libraries based on custom content type with "Link To a Document"
  • Added additional refresh after changes of URL fields in SharePoint list items to accelerate refresh of updates
  • Improved catch of errors if link cannot be checked
  • Added option to set that ReplaceMagic should close after XML configuration files processing.
  • Added option to trigger notification popup after XML configuration files processing is completed

 

Ver. 2023.5 - Files with special characters, Excel optimization...

New in version 2023.5 (recommended upgrade)

  • Improved processing of files with special characters like % and #.
    Until this version this was possible only when legacy SharePoint mode was used. From this version this will work also when legacy mode is not selected. Previously, ReplaceMagic would report:
    "File with % in name cannot be saved; if possible switch to SharePoint Legacy mode"
  • Fixed bug in parameter removal functionality (parameter was removed but link was not updated)
  • Further optimizations in processing Excel files (LinkSources...)

Ver. 2023.4 - Further improvements included...

What is new:

  • Fixed bug that during processing documents stored non-SharePoint location number of working processes is reduced due to SharePoint throttling mitigation actions.
  • Fixed bug that in rare case scanning results are not shown due to wrong counter of active threads.

Ver. 2023.3.3 - Updated WebView2 components

What is new in 2023.3.3:

  • Updated WebView2 components

Ver. 2023.3.2 - Included missing DLLs for WebLogon

What is new in 2023.3.2:

  • Included missing DLLs for WebLogon authentication (x64, x86, arm64)

Ver. 2023.3.1 - Improved processing of PowerQueries in Excel

What is new in 2023.3.1:

  • Improved processing of PowerQueries in Excel (recommended update if you have PowerQueries)

Ver. 2023.3 - SharePoint check of broken links and minor improvements

What is new in 2023.3:

  • Cleaned-up SharePoint relative shared links to exclude parts like /:x:/s/ for check of broken links.
  • Occasionally when you add SharePoint site, it will not be immediately visible in SharePoint treeview. Including additional text to explain workaround (close and re-open form with SharePoint treeview which will refresh entries):

Ver. 2023.2 - SharePoint throttling and ReplaceMagic - new functionality

What is new in 2023.2:

  • Fixed problem when on DFS share processing is stopping after first folder found with Access Denied permissions.
    As outside of ReplaceMagic components are used for creation of list of files for scanning, we cannot show skipped folders directly in ReplaceMagic but AccessDeniedLocations.log file will be created in c:\users\username\appdata\roaming\replacemagic\logs where you can find what was skipped. If no file is found that means that there were no locations with Access Denied. Failback location is c:\Temp.
  • Improved check of relative links with documents in SharePoint.
  • Extended filtering of temporary files (starting with ~$) uploaded to the SharePoint.
  • Added option to remove parameters from URL which is useful in case of migrations to SharePoint when there are URLs like: https://old.system.com/sites/newsitename/path/to/file/somefile.xlsx?d=w152a583596ef4cc198abe15ad350117d as after migration parameter d will point to old document ID which will not work anymore. To set parameters for removal use Configuration => Misc:

    What is new?
    With this configuration ReplaceMagic will remove d and p parameters from URL. Separator between parameters is | and this will work only for links in Hyperlinks section. Replacement is not case-sensitive so if you specify d=, ReplaceMagic will replace parameter d= but also D=.
    Prerequisite: you will need to provide search&replace strings as otherwise replacement process cannot start and changes in hyperlinks need to be selected.
  • Further reduction of requests to SharePoint to reduce workload triggered by ReplaceMagic.
  • Fixed bug that in rare cases under heavy throttling ReplaceMagic can close.
  • In SharePoint article https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online (last update from 03/20/2023; page is regularly updated) Microsoft is stating that beside user throttling there will be application throttling also. Every application will have own limits per tenant no mater if Microsoft Graph, CSOM or REST is used (ReplaceMagic is using CSOM and REST). Limits are as following (taken from MSFT site):

    Also different resource unit costs per request are defined:

    (example is for Microsoft Graph, where CSOM and REST are even more "expensive"). To translate to ReplaceMagic terminology - scanning is "easy" request as we need only to download file but in case of replacements multiple requests are required for:
    - Meta data preparation
    - Download file
    - Upload changed file
    - Optionally, set meta data back (last modification date, editor, status of file, version...)
    This will cause that replacement will require more than few request which will be taken from your quota. To reduce risk of throttling, we are strongly recommending not to use more than 2 documents in parallel (default is 4) as there will be great chance that you will be throttling. In case of throttling ReplaceMagic will automatically reduce parallelism to 1 (sequential processing) and if parameter Optimize workload is selected ReplaceMagic will start to increase parallelism after defined number of processed documents (new value 100 (reduced from 500) without throttling.
    According to Microsoft documentation, when throttling is happening there has to be used Retry-After parameter which will stop processing for SharePoint requested duration value.

  • Added parameter "Use SharePoint retry-after recommendation" - when SharePoint throttles you, it will send duration during which processing cannot continue. By using this parameter, ReplaceMagic will stop processing for SharePoint requested period and continue afterwards. Default: selected.

  • In case that you do not want to use SharePoint retry-after parameters values via parameter "Throttling retry-after period" you can define own wait period (default: 120). This parameter is only visible if parameter "Use SharePoint retry-after recommendation" is unchecked:

    Due to this parameter when ReplaceMagic is first time throttled, there will be pause of 120 seconds before processing can continue and you will see that information in progress bar. Using this and above parameter we are protecting your processing to be totally stopped and to have as less skipped documents due to throttling as possible.