Here is a list of critical updates released by Salesforce that have potentially impact your Frisbii configuration.
Please check whether this applies to you and follow the instructions if it does.
We'll be updating this article regularly.
Withdrawal of Discover reports
Discover reports will be withdrawn. The information below describes the actions required to prepare for the transition to the replacement product, Datorama Reports for Marketing Cloud, featuring a more robust reporting capability.
When: The withdrawal date for Discover reports has been effective since April1, 2022.
Case study: preparing for the withdrawal of Discover: At the very least, carry out the following actions before April 2022:
Download the appropriate Discover reports with data older than one year and store them in a different location.
Check scheduled Discover reports to see which ones you need. Delete unnecessary scheduled reports.
Review the documentation on activating Datorama Reports for Marketing Cloud.
Create a list of all business-critical reports to be recreated in Datorama Reports for Marketing Cloud and start creating them as soon as possible.
Datorama reports for Marketing Cloud
Case study: Before you start using Datorama Reports for Marketing Cloud, ask your administrator to assign the required user role to your account. Once you have the user role, assign permissions for actions that can be performed in Dashboards, PivotTables and Reports.
Access Datorama reports for Marketing Cloud
To access Datorama Reports for Marketing Cloud, you must have the required user role assigned to your account. When you assign the user role, you can also assign permissions that are allowed in Datorama Reports for Marketing Cloud. For example, you can create pivot tables, but you can't edit or save them.
User roles and permissions in Datorama reports for Marketing Cloud
When using Datorama Reports for Marketing Cloud, the Datorama Reports for Marketing Cloud user role must be assigned to your account. The user role has the following permissions: Access, View & Export, Schedule, and Create & Modify.
Salesforce multi-factor authentication
Where:At Salesforce, customer trust is our priority. Security threats are constantly evolving, and the types of attack that can cripple a business and exploit consumer data are on the rise. Strong security measures have never been more important.
When: That's why, as of February 1, 2022, Salesforce requires all customers to use multi-factor authentication (MFA) to access Salesforce products. MFA is one of the simplest and most effective tools for strengthening connection security, and protecting your company and your data against security threats.
Upgrade to tenant-specific endpoint authentication
Case study: To improve the performance of the Marketing Cloud platform, sub-domains are automatically assigned to all Marketing Cloud customers, improving API performance and speeding up the Marketing Cloud experience. It is required for certain Marketing Cloud data centers. You can update connected business units that don't yet use tenant-specific endpoint (TSE) authentication yourself, without disrupting existing connections. All new connections automatically use TSE authentication.
Tips for using hypertext link formula fields
How: If you have custom formula fields that contain a HYPERLINK function, the server generates an HTML anchor for the link. For example, this function: HYPERLINK("/apex/VF_TEST", "VFLINK",'_self') generates this HTML output: <a href="/apex/VF_TEST" target="_self">VFLINK</a>. If the HYPERLINK function doesn't contain a target attribute, it defaults to the target="_blank" value of the generated HTML output. A "_blank" value opens the link in a new window or tab, outside Lightning Experience or Lightning Console.
Subscribing users, groups and roles to reports in Lightning Experience
Who: Subscribe, or subscribe other users, groups or roles to receive updated report results by e-mail at the frequency of your choice.
Case study: For example, instead of manually running and e-mailing your team your weekly sales report, subscribe the team to the report and send it to all members at the beginning of the week (preferably on Monday morning).
Steps:
- In the Reports tab, or from the report run page, click on
| Subscribe. - In the Modify subscription window, set the subscription frequency.
For the weekly sales report, choose a weekly subscription with delivery on Monday at 8:00 am. - To send the report results as an attached file, click on Attach file. Select Formatted report (.xlsx format) or Report details (.csx format). For .csv attachments, selection of the encoding type is optional. Once you've selected the attachment type, click Save.
- You are automatically selected under Recipients. To add or remove other users, click on Edit recipients. Select from the available entity types, then start typing to display all matching names. Only users, groups or roles authorized to access the report are displayed in the results list. Select the corresponding options, then click on Add. Add other users, groups or roles, if necessary, then close the Edit Recipients window.
The updated report is sent to each recipient at the e-mail address defined in Settings | E-mail | My e-mail settings. If no e-mail address is defined in My e-mail settings, the updated report is sent to the e-mail address defined in the recipient's Salesforce user record. - Under Run report, specify the perspective used when running the report.
- Me: you run the report and recipients see the same report data as you.
- Other person: recipients display the same report data as the selected person. The person must be authorized to run the report and have access to it.
- You can add conditions. Conditions are evaluated when the report is run at the frequency you define. The report is sent by e-mail only if the conditions are met. For each condition, select an aggregation measure, an operator and the value to be matched. You can add up to 5 conditions. The host names of your Salesforce organization will change. Are you ready?
- Click on Save.
Developer blog
The set of domains used by Salesforce will change in Winter 23 for sandbox and non-prod orgs (from August 2022), and in Spring 23 for all other orgs (from February 2023). This change may affect your code, configurations, API integrations, SSO, documentation and bookmarks.