Product Updates

NotificationsWe've seen how intrusive the notifications could be in situations with varying WiFi quality, and have redesigned how the notifications work. Confirmations show as a small grey single-line message (for example, "checklist deleted"), while important issues show as full-width, horizontal bars.Image performanceUploading of images has been a massive success, with thousands of images uploaded so far. Pages with many high-quality images could cause the app to fail, but we have now improved the performance. We'll continue improving the performance in the coming releases.Checklist performanceWhen many users each had many checklists, the app would sometimes load slower. The app now loads with the same speed regardless of the number of checklists.

The scanner function is improvedWe've rolled out to customers and assets that have very different tag and nameplate structures. To improve tag scanning, we have made a separate tag scanning workflow to better support these cases. This change does not affect tag scanning at plants where the functionality already worked well.

We're happy to announce the general availability of the Cognite Data Fusion API v1.Please help us improve our products by letting us know what you think or if you have any issues. To send us feedback, or if you need help, contact support@cognite.com. New featuresExternal IDThe external ID field, (externalId), is available in API v1 across multiple core resources: time series, assets, events, and files. You can now define a unique identifier for each data object in Cognite Data Fusion (CDF) as an optional extension to the existing id field.The purpose of external IDs is to:Insert data without creating duplicate entries. Avoid extra lookups when updating data. Maintain relationships between data objects from source systems. Give you a way of performing key-value lookups with keys you control, and that works the same across core resources.Learn more about external IDs here.3D APIYou can now upload and process 3D models with the 3D API. Initially, we support the upload of 3D models in the FBX format. More CAD formats will be added soon.In CDF, a model is a container holding many revisions. For example, you can have a model named “Compressor”, and you can upload multiple revisions under that model as the design changes over time. When you create a revision, first upload the actual 3D file using the Files API, then create a new revision for the model linked to this file.When you upload a new revision, CDF needs to process the 3D data to optimize it for rendering. This can take some time. We provide a status string in the revision object so you can follow the progress of the processing.A 3D model is typically built up as a hierarchical structure. You can extract the 3D node hierarchy, and also create links from the 3D nodes to nodes in CDF’s asset hierarchy. This can be used to allow a user to click on equipment in a larger 3D model and access related sensor values or documentation.The 3D models are typically rendered in a web application using our 3D viewer component called REVEAL. REVEAL loads a 3D model from CDF and renders it with high performance in a web browser. REVEAL has no default UI but provides a JavaScript API for flexible integration into different types of web applications. ImprovementsStructural improvementsThe new version of the API has a consistent API design across all resource types, including:Consistent design and behavior for standard endpoints, with functionality such as insert, search, list, partial updates, delete. Common naming of query parameters, and request and response attributes. Shared pagination pattern with limit and cursor. Consistent use of response codes. Single error type for API. Documentation improvements: constraint definitions for input parameters, required fields, more detailed attribute documentation, A simplified API that provides one way to perform specific tasks.Search and filtering improvementsYou can now filter on metadata and source in search, list, and filter operations for assets, events, and files.Time series allow for non-unique namesThe time series name attribute no longer has to be unique, and you can use the attribute as a display name instead of for lookup.To define unique identifiers for time series, use the new externalId attribute. For time series created through earlier API versions, the externalId field in API v1 will automatically be populated with the value of the name field. The time series you create with API v1 will require setting the new legacyName attribute to be discoverable by older API versions.Safe asset deletionPreviously, Aseet Delete API, due to its implicit recursive nature, allowed for unintentional removal of entire asset trees. We changed this operation to be more explicit by modifying the default behavior to delete only specific leaf nodes of the asset tree. The new parameter recursive:true allows you to explicitly enable recursive deletion of an entire asset subtree.Asset subtree query removalSupport for querying asset subtrees has been removed from the API. Instead, we introduced new filters that allow for narrowing down results to a specific list of root assets. A functionality similar to querying asset subtrees will be available through SDKs. This change is an enabler for introducing support for mutable asset hierarchies in the future.Service accountsUsers from previous API versions are converted to service accounts in API v1. Service accounts represent an application or service communicating with the CDF API. Each service account should represent a single application instance.Identity and access management - limitsThe new release limits the number of IAM (Identity and Access Management) resources you can create. If you exceed the limits, you need to remove existing resources before you can create new ones:Number of API keys per service account: 5. Number of service accounts per project: 700. Number of groups per project: 50 (undeleted groups). Number of security categories per project: 1000.New SDK versionsNew versions of Cognite's official SDKs supporting API v1:Python SDK 1.0.0(opens new window) JavaScript SDK 2.0.0(opens new window)New API versioningWith this release, Cognite is excited to introduce a new versioning scheme for our APIs. Starting now, we will use only major versions for our API (e.g., v1, v2). We will release a new major version only if we introduce changes that are not backward compatible and may affect existing clients.When you develop code using the CDF API, please accommodate for backward compatible (“non-breaking”) changes to ensure your application keeps working as we introduce new features and improvements.Click here to learn more about API versioning, our policy for backwards compatibility, and the end-of-life schedule for our APIs.Deprecating API 0.3-0.6The following API versions are scheduled for end-of-life. If you have applications, solutions, or demos using these APIs and SDKs, you need to migrate to the current stable API and accompanying SDKs. If you have any questions or need assistance please contact support@cognite.comThe APIs will not be available after their end-of-life dates.API version SDK version End-of-life date API 0.5 API 0.6 Python SDK 0.x.x or earlier JavaScript SDK 1.x.x or earlier January 02, 2020 API 0.3 API 0.4 Python SDK 0.11.x or earlier September 10, 2019  

New loading screenWe've introduced a new loading screen in line with Cognite brand identity.Trend y-axis now handles large numbers betterWhen a time series y-axis range had large numbers (typically 10.000 and higher), the charts could look cluttered. We are now displaying large numbers by shortening them to 10k for 10.000, and 1M for 1.000.000.

Delete checklists warningWe've received feedback that it was too easy to unintentionally delete checklists that others were still working on. You now get a warning if you try to delete a checklist that others could still be using. The logic remains the same: if you created a checklist, you can delete it, but that makes the checklist unavailable for others. If you did not create the checklist, you can not delete it (but you can choose to leave the checklist).Manage multiple checklistsIt is now easier to switch between multiple checklists on mobile devices. Click the checklist title to pull down a list of checklists and select the checklist you are looking for.

Multiple states on checklist items Checklist items can now have multiple states. When you are collaborating with others about a checklist, you can, for example: Use a "started" state to prevent others from starting on the same items. Use multiple states to control progress (for example, "started", "started in field", "finished in field", "completed")

Tag description in checklists - We've received feedback that checklist items were difficult to relate to without the description field. We've updated the way we show tags in checklists to include the tag description field.Pre-fixes in checklist itemsTo make it easier to add tag-based checklists from certain other systems, you can now add checklist items with prefixes. For example, if your work management tool (e.g., SAP or Workmate) uses a prefix for each tag (MyPlant-21PT1019), you don't have to remove the prefix in Excel or other tools before you create a checklist. You can paste the tag list, including the prefixes, directly into the tag field.Clicking other tags in the 3D viewWe have fixed an issue where it could be a problem identifying tags when clicking on another asset in the 3D view. It is now easier to click nearby tags and find out what the item is or navigate to the tag directly.Checklists now include the name of who checked it (desktop only)When you collaborate with others, it can be convenient to see who has performed each task. On the desktop, you can now see who checked an item and also when the item was checked. The information is also included when you export the checklist to PDF.