Released on March 17, 2026
Internal Release
This happened when the user removed one or more columns from minutes. Then, if he inserted these fields back, but at a position BEFORE their original position, an error occurred.
There were 3 translation errors where C# didn't behave exactly like old VB .NET code (handling of null values mostly). That have been fixed globally to ensure the behavior is now similar in both languages.