Salesforce Wave Analytics is a cloud-based platform for connecting data from multiple sources, creating interactive views of that data, and sharing those views in dashboards. It's a better way to distribute insight to business users so they can understand and take action on changing information.

1. Ceptes R&D
Chandan
Mobin
Gowthami
Jagadeesh
Vijay
Prateek
Salesforce Wave Analytics

2. Salesforce Wave Analytics

3. Wave Analytics Assets
❖ Apps
❖ Dashboards
❖ Lenses
❖ DatasetsDevelop on the Wave Platform
❖ The Wave REST API
❖ Salesforce Analytics Query Language (SAQL)
Permission sets and permission set licenses

4. SAQL Query performance

5. ❖ All customers receive Wave Analytics updates on the same schedule, regardless of instance.
❖ Accessibility features not supported.
❖ Packaging and MetaData API does not supported.
❖ Limited field level security.
❖ Wave Analytics has been localized with the following exceptions.
➢ Do not support right-to-left languages, such as Arabic and Hebrew.
➢ A subset of error messages is available only in English.
➢ The mobile iOS app includes only English versions of sample datasets and dashboards.
Wave Analytics Limitations

6. Platform Cache
Platform Cache is a memory layer that stores Salesforce session and org data for later access.
In short, think of Platform Cache as RAM for cloud application.
Cache Types
❖ Org Cache
❖ Session Cache

7. When to use platform cache
Org cache:
❖ Data that is very likely to be needed again by multiple users
❖ Data that is changed frequently but changed infrequently
Session cache:
❖ Data that is very likely to be needed again across cross transactions throughout the session
❖ Data that is only needed in particular user session

8. Limitations
❖ Platform cache is not a durable store
❖ Data put to the cache may not be there when you try to get it
❖ Application server shutdown
❖ Capacity Eviction
❖ Service Protection

9. Custom Metadata
Deployable Objects and Data (including Managed Packages).
Not editable via Apex (but updatable via Metadata API).
Does not count towards query limits.
Public/Protected Visibility in managed package.
Cached after first head.
Complex data types(including lookups).
Ref: https://github.com/forcedotcom/CustomMetadataLoader

10. Why CMT and not Custom setting or Custom object?
Key Drivers
Portability
Traceability
Leverage Metadata API deployment tools (change sets).
Eliminate human errors.
Extensibility of architecture to support automated deployments through CI.

11. Comparison Table

12. Configuration objects