Tell us what features you’d like to see and support other ideas by upvoting them! Share your ideas in a user story format like: As a ˂role˃, I want to ˂function˃, so that ˂benefit˃. This will help us better understand your requirements and increase the chance of others voting for your request.
Normally, when we create a checklist in Infield we organize the tasks and groups in the right order for the operators to quickly fill the checklist and answer the tasks.We want to be able to auto-expand the next group of tasks when the user finishes the previous task and auto-collapse the group of tasks when the user finishes every task.
Yoojung Kim at Clear Lake requested the ability to view documents (particularly P&IDs) in grayscale in Canvas. Some P&IDs have very light colors, and switching to grayscale enables the user to view them more easily. I envision this as a toggle similar to toggling on/off annotations.
Want to create a component out of Canvas to be used in interal applications
Using the following models as an example:In space "imdb_core":type PersonType {typename: String!people: [Person] @reverseDirectRelation(throughProperty: "personType")}type Person {personType: PersonTypename: String!}Extension Model in space "imdb_ext":type Actor@view(rawFilter: {nested: {scope: ["imdb_core", "Person/v1", "personType"]filter: {equals: {property: ["imdb_core", "PersonType/v1", "typename"]value: "Actor"}}}}) {Name: String! @mapping(space: "imdb_core", container: "Person", property: "name")Salary: Float}Populate instances into space: imdb_core using the Person ViewPopulate instances into the Actor View: Via the API, you do not need to specify the mandatory Name property as the instance already exists. See example screen shot. If you create a new instance, you do need to specify the mandatory properties. The API works as expected. Via transformations, you will need to specify the mandatory Name property in either case. SLB has raised that this behavior is inconsistent. In order to populate extension types, users will need to respecify the Mandatory properties of the base types in order to leverage transformations.
I see value of putting in hotlinks in several tasks in checklists for easy access to information needed for executing the task. The links works today if you just put it in the description of the task, but it does not look that good. Many of the links we have internal in our company is long and not that descriptive.Here are an example of what I mean. Cool new feature in InFieldInstead ofhttps://youtu.be/dQw4w9WgXcQ?si=meinOUMHX6612TqH
I have an idea to enrich the functionality and possibilities in checklists. When you make a task in a Template you should have the opportunity to trigger the task on an event in CDF. It is much the same as we trigger a task on a scheduled time today, but it need a bit more logic.An example can be that an transmitter are drifting and needs to be washed on a specific value. We have on the oil rig I work at an analyzer that is sensitive to growth of algae from sea water, and therefore have a false positive on chlorine. We have an High High alarm that trips our SRU package, so we need to wash off the algae before the value from the transmitter reach this HH alarm. Since this transmitter have a H alarm at 320mV and a HH alarm at 350 while “normal” value is about 190-210 we usually wash this at 250mV. Today CCR personnel see the value rises and call instrument techs to wash it. So if we instead could make an task in our template that generate a checklist-task to wash the analyzer and register if we change filter upstream, value before/after and so on if process value of the transmitter exceeds 250mV, There are many other events that also will be interesting if we have this opportunity.Another example can be that there is a new version of a document pushed to CDF that you should read, and register that you have read it. or if you should print it and update a paper folder.I really think that the opportunities to automate manual tasks will be many with this functionality. If there are questions don’t hesitate to contact me.
If you expand a file that has both portrait and landscape pages in one file to Canvas, the file will be displayed smaller when the portrait and landscape orientations are switched when pagination is performed.Will I be able to view such files in Canvas without any problems?
When using time series data, there are often situations where you want to get point in time for each day.For example, for time series A, which records the accumulated value, the raw data at 9 o'clock on 1/1, the raw data at 9 o'clock on 1/2, and so on.Even if you specify "Granularity=1d" using the SDK, the data obtained is aggregated, so there is a discrepancy from the raw data.Therefore, when I acquire raw data with daily granularity, I pick up the raw data as of 9 o'clock on 1/1 after acquiring raw data with fine granularity.This is very tedious and time-consuming, so I want an easy way to get the raw data at a specific time from the SDK options or UI.
Do you have the ability to hide left hand navigation items in the different workspaces? For example if your organization isn’t using Customer Apps (BETA) can you hide that from the menu options?
In teh table Data management > Data models, theire is no mean to fully visualise the description that has been providd for each data model available : no hover on the line, and the wide of the table is limited.This description should also be available on he screen in the header of the data model when you click on it
For Search, want ability to hide annotations on the preview of the file like you could in Data Explorer.
Hi! It would be great to have a possibility to add / change the placeholder text for Cognite functions. Example:It would be great to be able to add placeholder from code.
When making calls to the Cognite API, successful calls provide no confirmation of success. HTTP Response 200 would be helpful for asserting successful API requests. One point of uncertainty for us is when passing multiple External ID’s to delete row records in a staging table, if some ID’s are incorrectly identified, we aren’t receiving any feedback to indicate 100% success.We’ve read that when passing batches, there should be a return item indicating which records failed, but that is not our experience. Note: this is using the Cognite SDK.
HiFor a dashboard use case we are working on I want to extract a list of the column names in each raw table we have in our staging area. At the moment, it does not seem to be a way of doing this. I have made two very hacky ways of accessing this information (see the code example below), but they are either very time consuming because of inferring the raw schema, or it does not return anything, because the table has two many columns and it times out. This makes this method unfeasible when running the scripts for our whole environment, which would need to happen regularly. I feel like there has to be a better way of doing this. I know raw is a schemaless service, but the columns do exist. Having this information would greatly improve our efforts in getting a better overview of our data.from pydantic import BaseModel, Fieldclass RawTable(BaseModel): database: str table: str def to_friendly_name(self) -> str: return f"{self.database}.{self.table}" def get_inferred_raw_schema(self, cognite_client) -> Dict[str, Any]: schema = cognite_client.transformations.preview( query=f"select * from `{self.database}`.`{self.table}` limit 100" ) return schema.schema.dump() def get_raw_schema_from_profiler(self, cognite_client) -> List[str]: res = cognite_client.post( url="/api/v1/projects/[INSERT_PROJECT]/profiler/raw", json={"database": self.database, "table": self.table, "limit": 1000} ) return list(res.json()["columns"].keys()) Thank you!Sebastian
We are doing quite a few transformations on larger FDM-tables, and are experiencing them to be a lot slower than what is to be expected. From my understanding CDF is reading some rows a at a time from the database, doing a standard database operation (with Spark), and writing back to the database. The read operation is very slow (for one transform I am running now read speed is 1600 rows/s). Is it possible to write a transformation (with standard SQL) that will be run in-database, that avoids the slow read? This would be especially beneficial for FDM to FDM transformations, as this would reduce time from minutes to milliseconds for some of our transformations.
When on-boarding a new user can we set a way to define the search location for them to start in out of the gate? Currently in our configuration we have to have each user select the location in which they should start searching from. Our users are spread across different locations which may have different search locations. Setting them all manually isn’t ideal.
As a continuous improvement engineer, I’d like to be able to use Industrial Canvas to view charts with an overlay of events like we do today but in addition, be able to add a list/table of events that meet my filtered criteria to the canvas. The time frame criteria could be the same as the timeframe applied to all the charts on the canvas.
This is a request from customers, where they would like to have additional colours in the palette for industrial canvas.
If I “traveled” through multiple 360 images and then decide to exit 360 image view, it seems to put me back where I started in the CAD model. Users want to be at the same coordinates in the CAD model as the 360 image they are exiting. Also, even if I don’t “travel” around the plant and am toggling between 360 and CAD in the same place, sometimes the angle seems to be different, e.g. I exit the 360 view and am rotated by 90 degrees.
Suggestion: Add a setting to customize the default view on the Overview tab.Benefit: This would save users time and clicks by allowing them to set their most frequently used view (e.g., Checklists) as the default instead of Work Orders.
As an operator, I want to optimize the number of tasks shown in the space available, so it would be easier to navigate through them. This is a suggestion from Celanese users: to maximize the number of tasks shown on screen. In this screenshot we can only see 3 tasks. It would improve the user experience if there were, for example, the task name and 2 small buttons right beside it, occupying only 1 line. It would make it easier to read the tasks, especially in checklists that have numerous tasks to be filled.
When a contextualized P&ID is upgraded, the position of the device is often slightly off.In that case, it would be very helpful if you could respond by moving the contextualization frame without having to redo the contextualization.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK