![]() ![]() Time Comparision widgets returning 0% change in Email Overview dashboard Metric values on rows of the inner-most dimension (highest granularity) are sorted correctly. Sorting is not working correctly on Aggregated values in the Pivot Table widget. Sorting function not working on aggregated values in Pivot Table widget Please try again or contact support for help.\" When trying to create a new collection from template an error rises: \"An unexpected error occurred. The Page header where the name, the date range, the filters, and other settings are displayed is not sliding when switching between View and Edit mode for a Custom Widget.Įrror when creating a collection from template Sending Push Transactional Messages will not work if ContactKey is used in the Payload and MID (Business Unit) is different from EID (Enterprise/Top Level Account).Ĭustom Widget | Page header remains visible in Edit mode Push Transactional Messages will not work if ContactKey is used in the Payload The unexpected behavior, in that case, happened while the \"Get Prospect Data\" in the extended properties. We noticed occasional failures of Salesforce Pardot Data Streams Jobs with an \"Unknown\" Error. Salesforce Pardot | Unknown Errors from Salesforce Pardot connector\'s Job An attempt to do so results in the error, \"No available SmartLenses for specific data stream\" The YouTube Ads SmartLenses app is currently unable to be installed. Youtube Ads Smartlenses cannot be installed from Marketplace Instead they\'ll display a message, something like \"Unable to load data please contact support for more information.\" ![]() If a query contains too many values that are being filtered on, then the widget being queried (such as a table widget) will not load. Too many values being filtered on causes widgets to fail A user from account Y, not having access to account X, attempts to view the log and receives an error The activity log contains rows from a user in account X who performed an actionĤ. Later, the workspace is moved to account Yģ. The given workspace of the entity (DS, report) was once under account XĢ. One example of a scenario which creates an unviewable log is as follows:ġ. In limited circumstances, a Datorama user may not be able to view the activity log of an entity such as a data stream or report, if that activity log contains entries with details that the viewing user does not have permission to access. Users cannot view Activity Logs that contain records which the user cannot access
0 Comments
Leave a Reply. |