Suggest features, upvote favorites, and use the user story format: > As a [role], I want to [action], so that [benefit]. Help us build what you need - post your idea now!
What you should know submitting product ideas to our product team
Share your product ideas with the community and our product team
ProblemSmart Factory is a Flows custom app that runs inside the CDF iframe with hideShell=true. In that mode users cannot open the Fusion account menu to sign out.HostAppAPI from connectToHostApp (@cognite/app-sdk) already exposes getAccessToken(), getProject(), getBaseUrl(), navigateExternal, and setHideShell (see Flows Auth API). It does not provide a way to end the Cognite Auth / Fusion session from the app:There is no logout() (or similar) on HostAppAPI. Cognite Auth RP-initiated logout (end_session_endpoint at https://auth.cognite.com/oauth2/sessions/logout) expects an id_token_hint. The host only exposes a CDF access token via getAccessToken(), not an ID token. Fusion’s own logout uses that end-session endpoint with id_token_hint and post_logout_redirect_uri. From the iframe we cannot obtain a valid id_token_hint.We also cannot use setHideShell(false) just to expose Cognite’s logout UI. Proposed solutionExtend HostAppAPI with one of:logout(options?) – the host clears the Cognite Auth / Fusion session and sends the user to the usual post-logout entry (for example the org selector), with a documented redirect option if that fits. getIdToken()– so the app can call the OIDC end-session endpoint with a proper id_token_hint via navigateExternal.Either approach would let custom apps sign the user out while the shell stays hidden.
SummaryLet Atlas create a Chart calculation from a natural-language request and plot the result as a time series chart.Today a user can build that calculation by hand in the Charts node editor (sources, constants, functions, and an output node), or ask Atlas to analyze stored time series. Atlas can embed a bar chart, KPI, table, or an existing Charts time series in a reply. It cannot turn a formula, for example a pressure difference, a unit conversion, or a scaled flow, into a calculation and show that calculated series on a line chart unless the result already exists as a time series in CDF. ProblemEngineers and operators compare derived signals as often as raw tags: pressure drop, API gravity, unit conversion, ratio of two flows, a moving average. Those series are usually not stored in CDF.The path today is manual: Find the source time series. Open Flows > Charts, create a chart, and add the series. Open Add data > Create calculation and wire sources, constants, and functions into an output node. Read the plot, then adjust the calculation if the result is wrong. Atlas already sits next to this work. In Charts, Agents can find data and discuss thresholds. In Ask Atlas AI, the agent can retrieve time series, run Analyze time series, or compute a conversion in the sandbox. The calculated values stay in the answer. The line chart still shows only stored series, so the user cannot see the derived trend against the raw tags.That gap shows up when: Two series are comparable only after a conversion (different units or a scale factor). The user wants several one-off calculations (difference, ratio, smoothed signal) without a library of persisted calculated time series. The user knows the engineering formula and the asset, and does not want to assemble the node graph. Current behavior Capability What exists today Charts calculation User builds a node graph: input time series, constants, functions, and a final output node. The output is plotted on the chart. One calculation can feed another. Schedule a calculation Save and Schedule writes the result as a time series and can be monitored. Requires schedule credentials. Atlas in Charts User opens Agents, picks an agent and locations, and asks questions about the chart (for example, adding a threshold). The agent does not create the calculation graph. Atlas chat visuals A reply can include a bar chart, KPI tile, table, or a Charts time series that already exists in CDF. Calculated series in chat The time series chart widget plots stored CDF time series. A calculated value is visible on that chart only if it is its own time series, or if the user builds it in Charts. Numeric calculations in Atlas Analyze time series, the Query tool, Run Python code, and Call Function can compute an answer. The language model is not the calculator. None of these tools creates a Charts calculation or plots the derived series. Proposed solution Add an Atlas capability that: Understands a request to derive and plot a time series. Resolves the source time series in CDF (including @ mentions and the active location filter). Builds a Charts calculation using the same primitives the node editor already supports: sources, constants, functions, and an output. Evaluates the calculation with the Charts calculation engine, not with the language model. Renders the output as a time series line chart, with the source series available on the same chart when that helps comparison. Lets the user open the result in Charts, inspect and edit the node graph, save the chart and only after an explicit confirmation; schedule it as a time series. The calculation definition must be inspectable. The user sees which series, constants, and functions Atlas used before treating the plot as correct.Example requests “Plot the pressure difference between PT-1019 and PT-1017 for the last 7 days.” “Convert this flow from tons per period to tons per hour and chart it next to the raw series.” “Show API gravity from @specific-gravity using 141.5 / SG − 131.5.” “Add a 1-hour moving average of bearing temperature on compressor C-205 to this chart.” User storyAs a reliability or process engineer using Cognite Data Fusion,I want Atlas to create a Charts calculation from my request and plot the result,so that I can see a derived trend (difference, conversion, ratio, or smoothed signal) without building the calculation by hand or storing a new time series first. Requirements Discovery and intent Atlas recognizes requests whose goal is a plotted derivation, including difference, sum, ratio, scale, unit conversion by a constant, and a function that Charts already exposes (for example a moving average). A request that only needs a number or a statistical conclusion continues to use the existing analysis tools. Atlas plots a calculation when the user asks to chart, plot, trend, compare visually, or add a series to a chart. The user can make the request from: Ask Atlas AI in the Flows workspace the Agents panel on an open chart @ mentions of a time series, asset, or activity are treated as pinned inputs and take precedence over name search. Location filters selected in the agent session limit which time series Atlas may use. Building the calculationAtlas resolves each input to a specific CDF time series (external ID or instance identity) before it builds the calculation. If more than one time series matches, or a required input, constant, unit, or time range is missing, Atlas asks a clarifying question and does not plot a guess. The calculation is a valid Charts calculation: one or more source nodes, optional constant nodes, function nodes supported by Charts, and exactly one output node for each plotted result. Arithmetic and function evaluation run in the Charts calculation engine (or the same engine Charts uses). The language model must not invent data points. The calculation records the output name, the formula in user language, the node graph, each source time series, each constant, and the time range used to render. When the request depends on aligning series with different timestamps, Atlas uses Charts automatic data alignment and states that it did so. A calculation that Charts cannot express (custom packages, a function that is not in the Charts library, or a formula that needs Cognite Functions) is declined with a short reason. Atlas does not approximate it with model-generated points. Chart output The output is a time series line chart of the calculation result over the requested range, or over the chart’s current range when the user is in Charts and does not name a range. Source series used in the calculation are available on the same chart so the user can compare raw and derived traces. The user can hide a source series without deleting the calculation. The chart shows the calculation name, unit when known, and a visible indication that the trace is calculated rather than a stored time series. In Ask Atlas AI, the chart is rendered in the reply and can be opened in Charts. In the Charts agent, the calculation is added to the open chart and appears both on the plot and in the calculation editor. The user can change the time range and the calculation re-evaluates for that range, the same way a manual Charts calculation does. Empty inputs, a divide-by-zero, or a range with no points produce an explicit message and an empty or partial plot. The chart does not show a fabricated line. Review, save, and schedule Before or alongside the plot, Atlas shows the series, constants, and functions it used, in language the user can check (for example “PT-1019 − PT-1017”). The user can open the calculation in the Charts node editor and change it. Edits update the plot. Saving the chart follows the existing Charts save behavior and permissions. Scheduling (Save and Schedule) and writing a new CDF time series happen only after the user explicitly confirms. Atlas pre-fills the calculation; it does not start a schedule on its own. One-off calculations that the user does not save do not create time series, schedules, or monitoring jobs. Access and safety Atlas can read only time series the signed-in user can read, and can create or update a chart only when that user can do so in Charts. The feature respects the same Atlas AI capabilities required to chat with an agent. Citations or source references identify the input time series so the user can open them in Search or Charts and verify the inputs. Quality of the result For the in-scope formulas below, the plotted values match the same calculation built manually in Charts on the same sources, constants, alignment setting, and time range. In-scope formulas for the first release: add, subtract, multiply, and divide two series or a series and a constant a constant scale or offset, including a stated unit conversion that is a single factor a chained expression that Charts can represent as ordered nodes (for example 141.5 / SG − 131.5) one Charts smoothing or resampling function if that function already exists in the calculation editor (confirm the exact function list with the Charts team) Atlas states the time range, alignment, and unit assumptions in the reply. In scope Natural-language creation of a Charts calculation and its line chart Ask Atlas AI and the agent panel inside Charts Inputs by name, by asset context, and by @ mention Clarifying questions when the series, constant, or range is ambiguous Inspectable node graph, open-in-Charts, and manual edit Explicit, user-confirmed save and schedule using the current Charts flows Parity with a manually built Charts calculation for the formulas Out of scope Persisting a calculated time series or starting a schedule without confirmation New calculation functions that Charts does not already support Cognite Functions, custom Python packages, or model-written code as the plotting engine Bulk generation of large chart libraries Monitoring and alerting on the new calculation, beyond the existing Charts monitoring flow the user starts themselves Bar charts, KPI tiles, and tables of non-time-series aggregates (already available) Animating or streaming the series beyond the live behavior Charts already has Changing who can read a time series
The ability to define a CogniteUnit on a column in a container is very powerful. However, there are many situations where we are not able to define one common unit for an entire column.One example is LCI/Equipment data. Properties like length, volume, weight will have different units for a massive compressor vs a tiny bolt. We want to avoid doing unit conversion on ingestion since it introduces added complexity and risk (how to handle that a unit is not specified in the source), and it will also require the end user to do the unit conversion to get the number on the unit from the source system. One possible approach could be to have a column with the CogniteUnit instanceid, and then instead of defining the fixed CogniteUnit for a column we define the column with the unit.
One of the more important properties for industrial data is the Engineering units of a value (unit of measure).Today we can add a CogniteUnit, both to a timeseries and to a column in a data model container, which will enable unit conversion on consumption.When we ingest the data from our source systems, we need to identify the unit as it is described in the source system, and then match it to the correct CogniteUnit. Many of our source systems do unfortunately not follow a standard for engineering units (leading to the need for the looooong alias list in the unit catalogue).But some of our systems specify the unit via a standard. For AkerBP it is mainly CFIHOS and OPC-UA (which really is UN/CEFACT unit codes)It would be very helpful to both being able to identify a unit via these standards when the unit is populated, but also when it is consumed.Eg: Temperature in Celsius isCFIHOS-60001435 CE/CEFACT/OPCUA unitID=4408652I can add the CFIHOS code to the alias list (we are doing this now), and it will solve our unit ingestion for CFIHOS codes.We could create a similar standard, like OPCUA-4408652But if I as a user need to find the unit for a specific code, it would be helpful if the unit code is also exposed via the CogniteUnit instance.Today I can only access (alias list is not exposed in the data model)Field Value externalId temperature:deg_c name DEG_C description Degree Celsius symbol °C quantity Temperature source qudt.org sourceReference https://qudt.org/vocab/unit/DEG_C version 2 createdTime 1724940140919 (2024-08-29 UTC) lastUpdatedTime 1777015910489 (2026-04-24 UTC) I will propose adding something likestandard_definitions: [CFIHOS-60001435, OPCUA-4408652]Or potentially a property per standard (but that can grow a lot)
Several Data model views contain large volumes of historical data, which can impact performance, scalability, and overall user experience. A potential improvement would be to implement a historical data archiving strategy by separating older records from active datasets.For example, records beyond a defined retention period could be moved to dedicated archive views, while primary views retain only the most recent and frequently accessed data. Another option would be to maintain a separate historical reporting layer specifically designed for long-term analysis and archival reporting.This approach would help improve query performance, reduce dataset sizes, and enhance usability for analytics and reporting tools. Users would benefit from faster data retrieval, shorter dashboard load times, and a more responsive self-service analytics experience, while also reducing processing overhead on the platform.
Hi, Is it possible to perhaps add a "warning" status to Extraction Pipelines? Sometimes it is nice to not just flag something as a failure but still something that should be flagged/raised.
I feel that when zooming in with the mouse wheel, the increment at which it zooms is too small. For instance, when I zoom into a canvas with 5 drawings it takes 15 mouse wheel up’s to get to the zoom level that I am able to read any one of those drawings. Then when zooming back out it takes 15 to see the whole canvas again.
RequestProvide the ability to change bounding box colors based on the status or metadata of the associated document, inspection data, or record.The goal is to make important status information visible directly within the working view, allowing users to recognize items that may require attention without opening each item individually.Problem / opportunityWhen reviewing documents or records together, users need a clear way to distinguish their status. For example, they may need to know whether a document is managed, whether it represents the latest revision, or whether an associated inspection is overdue.Status-based bounding box indicators would bring that context into the visual review, rather than requiring a separate status check for every item.Use Case Examples1. Managed versus unmanaged documentsUse different bounding box colors to distinguish documents identified as managed from those identified as unmanaged.Example: A user reviewing several documents could immediately identify which documents have a managed status and which require further verification.2. Latest versus older document revisionsUse bounding box colors to indicate whether a displayed document is the latest available revision or an older revision.Example: If a newer revision becomes available, the bounding box around the older document could change color to alert the user that the displayed revision should be reviewed.Important distinction: Managed status and revision status should remain separate attributes. A document could be managed but still represent an older revision.3. Inspection or record due datesUse bounding box colors to identify inspection data or records based on their due-date status.Example: A record could display one color when current, another when approaching its due date, and another when overdue.Proposed behaviorConfigurable rules: Allow colors to be associated with defined status values or conditions, rather than limiting the feature to a fixed set of use cases. Metadata-driven indicators: Base the indicator on the relevant status, revision information, or due date associated with the item. Visible explanation: Provide a legend and a tooltip or status label explaining what each indicator means. Status updates: Reflect changes to the underlying status when the associated data is refreshed. Multiple-status handling: Define how indicators behave when more than one condition applies, such as a document being both unmanaged and an older revision. Unknown-status handling: Clearly distinguish missing or unavailable status information from a confirmed current or acceptable status. Accessibility: Supplement color with a text label, icon, or border style so users do not have to rely on color alone.Expected valueThe intended benefits are to:Make document and record status easier to recognize at a glance. Reduce repetitive checks of individual items. Draw attention to outdated documents and overdue records. Support more informed document selection and review.
Its a need to have the schedules tab available for all users using InField. As a technician it is beneficial to see all upcoming check lists in a schedule view just as the lead technician is able to today. This gives a much better overview of all lists coming up in the next week.The only downside is that the technicians don’t need to set a check list to “Ready” status. Its proposed to give technicians a display version of schedules, without the possibility of setting lists to “Ready”.
Today there is no way to customize the way instances are ordered within hierarchy views. It would be beneficial with a method that could allow instances to be ordered to reflect the physical build of the monitoring system. Granted the information order can be delivered from the source into CDF, we can re-use the information to create a hierarchy view that more closely represents reality and what users may already be familiar with. However, in our case, we may have a sub-hierarchy (e.g. S1 data for Yggdrasil - Yggdrasil being the root of the hierarchy) that has one way of defining the order, while a different sub-hierarchy (e.g. SAS data for Yggdrasil) may not have exposed this information.
BackgroundWe want to build a new dashboard for our operations department in CDF Adaptive Experience. Our plan is to show existing time series, custom apps, and dashboards together as widgets in one place.While setting this up, we found the gaps below. We'd like to request the following features.1. Direct integration with CanvasCurrent: We can't create a direct link to a Canvas, and we can't embed a Canvas in the dashboard. Request: Allow Canvas content to be displayed on new dashboards in Adaptive Experience.2. Bulk import of edited charts or charts placed on a CanvasCurrent: Charts created on a Canvas (multiple charts) can't be embedded directly in the dashboard. The only options are to pull out each time series one by one, or to add a launcher through Flows. The launcher only opens a separate screen, which adds an extra step for users. Request: Let us paste edited charts into the dashboard. Ideally, a whole Canvas could be imported at once, with its charts registered automatically.3. Support for custom apps such as StreamlitCurrent: Streamlit apps and similar custom apps don't appear as options in the Dev environment. Request: We want all operations-related data to be visible on the new Adaptive Experience dashboard. To do this, we need to display custom apps there too, including the Streamlit apps our manufacturing department already uses.Expected BenefitsOperations staff can see all the information they need on one screen. Charts and apps we've already built can be reused, which saves time building dashboards. By running Atlas AI on the new dashboard, we expect to be able to do more advanced analysis. Users can find information faster, which supports wider use of CDF across the site.We'd appreciate it if you could consider these features. Thank you!
Hi Cognite Community,We have a requirement to provide configuration control over how data model objects are organized and presented in CDF Search and the Details view.As our industrial knowledge graph grows, an asset or equipment can be connected to many different object types, such as:Functional Location → Equipment → Time Series → Notifications → Work Orders → Maintenance Plans → Documents → Engineering Studies → MOCCDF already allows users to search and navigate connected resources. Data explorer - Cognite Docs However, for a large enterprise data model, the sequence in which these related objects are presented becomes important for usability and business context.We would like the ability for an administrator/data model owner to configure: Search pane object ordering Define which object types appear first and in what sequence. Details view tab ordering Configure the sequence of related-object tabs when a user opens an Asset, Equipment, Functional Location, or another object. Show/hide configuration Control which related object types should be visible in Search and Details views. Context-specific sequencing Allow the sequence to differ depending on the selected object type. For example, an Equipment view may prioritize Time Series, Notifications and Work Orders, while an Engineering Document may prioritize Assets, Equipment and related Documents. Model-driven configuration Ideally, this presentation configuration should be managed centrally as part of the CDF data model or application configuration rather than requiring custom UI development.CDF Views already provide a logical abstraction over containers and allow applications to consume a curated representation of the knowledge graph. Views - Cognite Docs We would like to understand whether a similar configurable mechanism exists, or is planned, for controlling how those objects and relationships are presented to users in CDF Search and Details views.This becomes particularly important as the knowledge graph expands to 60+ industrial datasets/object types. Without configurable sequencing, technically correct relationships may still result in a difficult user experience because the most relevant objects are not presented in a logical business sequence.Is this level of Search and Details-view configuration currently supported in CDF? If not, is it on the product roadmap?
I understand that updates older than 7 days may be discarded from the endpoint, which is perfectly fine. However, I’m wondering if it’s possible to determine when a cursor is older than the given limit, since updates older than 7 days are discarded. Based on my understanding of your Subscription API, it would simply continue iterating over the oldest available updates on the endpoint, which could result in missing important updates that occurred between the time of my cursor and the current oldest update. For the Subscription API to be fully functional, I believe it's essential to either receive a notification or an exception when using an expired cursor, be able to determine the age of a cursor, or somehow be assured that iterating from a cursor won't lead to lost data. Knowing the age of the cursor would be preferable, as it would allow us to gauge how much margin we have, but it should also be possible to receive a notification if an expired cursor is being used. Is this currently possible, or are there any plans to implement such a feature?
I have created this Feature Request to track the request raised here and to monitor its progress on behalf of the customers.IssueThe current limit of 100 in datapoint retrieveLatest API is causing performance issues when serving Angular dashboards due to multiple network calls.Solution proposedIncrease max number of time series returned in datapoint retrieveLatest API to 1000. Requester: priyanka.perera@cognite.comOrganization: Schlumberger
SummaryIntroduce a first-class NumericSeries object in Cognite CDF to natively represent depth-indexed data (measured depth, true vertical depth) and elapsed-time-indexed measurements (wireline elapsed time, drilling offsets in hours). Depth is a fundamental axis in upstream oil & gas, on par with time measurements. A NumericSeries would unlock more natural storage, querying, visualization, and analytics for a large portion of subsurface and drilling data.Why numeric indexes matter in Upstream Oil & GasNumeric indexes are the most widely used independent variables across the upstream domain: Drilling: MWD/LWD logs, drilling parameters vs. depth, trajectories, broomsticks, hole conditions Geology: lithology descriptions, stratigraphic tops, formations, facies vs. depth Petrophysics: wireline logs, core measurements, interpreted curves Reservoir & Completions: perforations, zones, intervals, properties vs. depth Elapsed time s/min/hr in addition to depth: wireline, well testing, drilling offsets Statistically, the largest share of subsurface data in upstream O&G is indexed by depth rather than time. Treating depth as a first-class concept would better reflect how domain experts think, work, and analyze data. Traditionally storage and infrastructure around depth and time logs in upstream software follows exactly the same pattern (everything except the index type).OptionsIn 2026 CDF currently has 3 potential options to store depth data - Sequences, Records, Files. Theoretically, CDF also allows to use TimeSeries, since index is integer. Integer index is interpreted as milli-seconds since 1970, however can hold any value, for example, millimeters, which is OK for depth and length measurements. One of viable options for future CDF is to fork TimeSeries into NumericSeries (or DepthSeries, or LengthSeries), since it seems to satisfy most of requirements for this kind of objectFeature comparison Requirement for numeric Sequences Records Files NumericSeries* Static schema (ex, trajectory) Yes Yes Yes Yes Flexible schema (most depth) Static only Static only Any Any Datasets 1000+ columns 200 max 1000 max Any Any Datasets 100k+ rows Too heavy All data <50M Any Any RAW and Transformations Yes No No Any Filtering by index Only int index Yes No Any Filtering by column values Yes Yes No Yes Aggregations No Yes No Yes Chunking/pagination Yes Yes No Yes Unit conversions No No, planned No Yes Python SDK Yes, now No, planned Yes Yes Extractor support Yes Yes, partial Yes Yes Value type - float Yes Yes Yes Yes Value type - float[], images No Via JSON Yes No Value type - text Yes Yes Yes Yes Value type - timestamp Yes Yes Yes Yes Available in CDF UI Yes, native Custom app Yes Custom app Value to CDF and Users Aligns CDF’s data model with upstream O&G data models (OSDU, WITSML, PPDM) Improves performance and usability for subsurface and drilling workflows Enables rich domain-specific applications and analytics Lowers total cost of ownership by simplifying data pipelines Strengthens CDF as a system of record for subsurface and drilling data
Today, a Simulator Routine in CDF requires a default value for each input variable.Currently, when running the Routine, I can either:Use the Routine default: 21 bar (see picture / comment below) Provide a custom value: 30.2 barWe need a third option:Use Model Value: when the user neither do not confirm the default nor provide a custom value, then do not send this variable as an input and let the simulation use the value already configured in the Simulator Model, in this example 20.28 bar (see picture / comment below)The key requirement is that not providing an input should be different from providing the Routine default.This would allow a Routine to override only the variables explicitly selected by the user while leaving all other values unchanged in the Simulator Model.Could Cognite please enable this? For our simulator use cases, this is a very important feature and should be prioritized.
Submitted on behalf of Raj Rathod, a senior principal reliability engineer. (There are also many use cases at the site that relate to safety checklists that would benefit from this product idea):As an InField template creator and user, I would like to be able to pull from a generic template that I can then link to any asset. As an example, I perform a visual inspection of many pieces of equipment across the site. I don’t want to have to create unique templates with the same 19 questions and have to tailor each of the line items to the asset. Instead, it would be convenient to have a generic template of those 19 questions that I can then assign the entire checklist to a specific asset rather than going down to the task level. In addition to this, it would be nice if the template or checklist could read the asset’s QR code and automatically pull up the basic asset information so that I can focus on the 19 questions for inspection purposes. This use case can also be used for safety checklists that have the same questions or fields across the site, regardless of the unit. A unit could pull up the generic template from a Site-wide “asset”, and then specify which unit and area within the unit the checklist can be tagged to.
Hi,In the Personal Learning Profile, there are many certifications, badges, and completed courses available. Is there any functionality for exporting this information, such as generating a PDF report or transcript that shows completed certifications, badges, and courses?Thanks!
In our use case, we modeled several related data categories, but they all appear as a flat list in Cognite Search, mixed with unrelated categories.From a usability perspective, it would be valuable to organize these related views under a custom parent category, with an expandable dropdown, similar to the existing grouping available for CogniteCore views.This would make navigation more intuitive and reduce category clutter, especially for Data Models containing multiple related entities.The request is to extend the existing category grouping functionality to custom Data Models, without requiring their views to inherit from CogniteCore views.
When we place multiple Charts side by side on Cognite Canvas, the X-axis and Y-axis labels become very small and hard to read (see the attached screenshot).The same problem occurs when we export a chart as a PNG file and paste it into Excel. The axis labels are too small to read clearly.We would like to request the following improvements:The ability to change the font size of the X-axis and Y-axis labels for Charts placed on Canvas The ability to change the axis label font size when viewing a chart on its own in Charts, with the change also applied to PNG exportsI apologize for the many requests, and thank you very much for your consideration.Best regards,
As per current condition, there is no labelling capability can be made in CDF Charts. Many charts have been created to support Canvas but to navigate to each chart to monitor the data or calculation that has been done is difficult since there is no labelling can be done on Charts (like canvas).
Simple Dashboard to display all the projects running in the organization - Project DashboardDetails of the projects when expanded
Hello,Currently when we search for the information “XXX” the system syncchronize all views records by looking for “XXX” in all the metadata of the views. So this a text link in the metadata.Our end suers would like to limit the number of clicks and synchronize all views including also all the contextualized data.Here below is an illustration of how it could improve the search experience when end users know there tags/assets
Currently, Charts and Canvas save changes automatically. We would also like to request a manual save function, such as a "Save" button.BackgroundWe have seen work being lost in both Charts and Canvas: Charts: the calculation source disappears As described in the related idea, Undo/Back Button for Calculation Editing, users sometimes find that their calculation source has suddenly disappeared while they are building complex formulas. When this happens, they have to start over from the beginning. Canvas: entered text is not saved As we reported in this community post, text entered on a Canvas sometimes disappears when we check it later. The change is also missing from the Canvas history, so we cannot keep a record. This has happened on several Canvases for some time. Unfortunately, these issues still occur. In some cases, the work does not seem to have been auto-saved at all, so everything is lost. This is very discouraging for users who have spent a lot of time and effort on their work.ProposalWe suggest adding a manual save function (for example, a "Save" button) in addition to auto-save. This would allow users to:Know for sure that their work has been saved Reduce the risk of losing work, especially when editing complex calculations or Canvas contentWe believe this feature, together with the undo/back function suggested in the related idea, would greatly improve the reliability of Charts and Canvas and give users more confidence in them.Thank you for your consideration.
If you perform the following actions in InField while status filters (“Ready,” “In Progress,” and “Done”) are set, I believe the status filters will automatically switch.① If you change the “Done” checklist to “In Progress,” only the “In Progress” filter will remain② If you change the “In Progress” checklist to “Done,” only the “Ready” filter will remain③ When you start reviewing a checklist marked as “Ready,” only the “In Progress” filter remainsRegarding point ③, I believe this is by design since it’s a natural flow considering the user’s workflow; however, we’ve received feedback from our users that points ① and ② are somewhat cumbersome to use.① ⇒ In our company, when an approver reviews the checklists Doned by an inspector, they sometimes review them all at once using the following workflow; however, this creates extra effort when instructing a re-inspection.Workflow OverviewConduct inspection (Inspector)⇒ Once the inspection is Done, change the checklist status to “Doned” (Inspector)Repeat this for each checklist.⇒ Review all Doned checklists at once (Approver)⇒ Change the status of checklists requiring re-inspection back to “In Progress” and instruct a re-inspection*Note: When changing the status from “Doned” back to “In Progress,” the filter defaults to “In Progress,” so we must apply the “Doned” filter again to review the next Doned checklist.② ⇒ In our company, inspectors often check multiple checklists simultaneously during a single round. However, when one checklist is Doned and the “Ready” filter is applied, we have to switch the status back to “In Progress” to view the checklists being processed in parallel.If this is an intentional design, it is fine as is; however, if there is no specific reason for this behavior, we would appreciate it if you could implement a specification that retains the filter settings for the scenarios described in ① and ②.I apologize for making such a detailed request, but I would appreciate it if you could consider this.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
