Daptiv Enhancements for August 12
We are deploying the following enhancements to Daptiv on August 12, 2022. This post is designed to help you understand how new and enhanced features can improve your Daptiv experience, and to guide you in making decisions about how to configure those features (if applicable). To facilitate training and testing ahead of this release, the features below will be deployed in Sandbox environments on Tuesday, August 8, 2022. The next Daptiv Release is September 9, 2022.
For detailed information about these and all Daptiv Features, see the Daptiv Online Help.
In addition to the fixes below, this release contains various background improvements that lay the groundwork for future enhancements. They should not have an impact on your current Daptiv experience.
OData Connector Fixes
This release includes fixes for the following OData Connector issues:
Data items with the detail aggregation set to Summarize were causing the connection to fail
Some field names were causing the connection to fail and stopped the dataset from refreshing correctly
The connection would fail when filters were used on fields that were not contained in query data items
Automatically created data sets with data item names that start with numbers or special characters were causing connection errors
Data modules were updating when adding or removing a column or changing a query name in the dataset
Datasets that included data from some custom Dynamic Applications were experiencing connection errors
These connection issues no longer occur.
Inconsistent page behavior opening workspace request approval notifications
Users were experiencing inconsistencies in the way workspace request approval notifications opened. These inconsistencies no longer occur.
Health data displayed on Home page
In the Favorite Workspaces pane on the Home page, workspace health data was being displayed for workspaces where Health was disabled. Now, that data is not displayed.
Clicking on a link to related project causes permission error
Clicking on a link to a related project caused an invalid permission error unless the user had the Can Administer Settings permission for the workspace. Users no longer need that permission to navigate between related projects.