Version: Next

🏴‍ Known Issues

This list includes all pending known issues not yet resolved.

[3 - Medium] Add new document: the DocList is not refreshed​

Description​

Internal: see TFS [#78718]
Sometimes when adding new documents in inPoint.Standalone the document list is not refreshed.

Workaround​

Internal: see TFS [#78718]
Select another folder and back to update the list of documents or restart the client.

[3 - Medium] OutlookAddIn/Settings: Requires a restart of the client to get back online when switching environments​

Description​

Internal: see TFS [#79316]
When switching environments in the Outlook-AddIn and the environments is offline first and then only later becomes online or when switching from an offline environment to an online environment the client inside of Outlook will not fully change the menu and icon to online.

Workaround​

Internal: see TFS [#79316]
Restart Outlook to resolve this issue.

[3 - Medium] inPoint.Core: Swagger ignores fields in CreateDocument​

Description​

Internal: see TFS [#79759]
The swagger page using "POST /api/v2/docs upload a new Document" sends the "fields" parameter so that it's not recognized on the server side. All the parameters must be in one "multipart/form-data" content called fields.

Workaround​

Internal: see TFS [#79759]
As a workaround it's possible to add a comment into the json body which will force "swagger" to use one "multipart-/form-data" content without splitting it.

Example:
Creating a document and setting two properties, "Type" and "State".
Image

The resulting request will have a body similar to this, the body contains all properties in "fields".
Image

Without the workaround, the request will look like this. The properties are added as own form-data entry.
(and not inside a property called "fields")
Image

[2 - High] Inconsistent DateTime handling with Reminders​

Description​

Internal: see TFS [#81871]
We currently have a known issue with Time-Handling for inPoint.API-Methods which were converted the gRPC.
Since gRPC always transfers Time in UTC sometimes but the values are not automatically converted into UTC.

Therefore, for some calls you might get a Time-Offset after save/load to the backend. For example, the ReminderData might have an Time-Offset (usually 1 or 2 hours - depending in your time zone) when adding the Reminder to the calendar and using gRPC (with is now the default).

Workaround​

Internal: see TFS [#81871]
For development, the workaround is to ignore the DateTimeKind of any date-times.

[4 - Low] Templates: Rendering issues on older outlook versions​

Description​

Internal: see TFS [#84240]
In some outlook versions, the new template header does not render correctly (mostly the H&S logo). These problems occur mostly in outlook versions that are out of support by Microsoft.

Workaround​

Internal: see TFS [#84240]
If you still need to get it to work, the header template (hs.inpoint.mail.header) can be edited manually to make it work.

[4 - Low] Setup fails with an error if not started as 'admin'​

Description​

Internal: see TFS [#84517]
If you try to install, repair or uninstall the setup of  inPoint.HybridStore or inPoint.Indexer by simple double clicking the msi file, the setup will later fail with an error:
"Info: SFXCA: Failed to create temp directory. Error code 5"

Workaround​

Internal: see TFS [#84517]
As workaround start an elevated command line and start the msi from there.  Using 'msiexec.exe' with the msi as parameter is not required, simple the full path and name of the msi will start it correctly.

[3 - Medium] LookupGetRows uses wrong Parameter length​

Internal: see OTRS [2026091701000054]
### Description
Internal: see TFS [#85262]
When using full-text search with lookups on a field of type VARCHAR, the search is limited to 50 characters.

Workaround​

Internal: see TFS [#85262]
To avoid this limitation, either change the field type to NVARCHAR or use fewer than 50 characters in the full-text search.