Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Hi @HanishSharma , Thank you for reaching out. Can you please send a copy of your workflow definition? We will look to recreate this error on our end. All the best, Kat
Hi @Sebastian Wolter , these features are available already in the latest version of the Cognite File Extractor.
Hi Shubham, I have reached out to the team with this feature request, and this is something we are considering for the short term roadmap. Support for a Regex filter has been added to the backlog. This will address your use case.All the best, Kat
Hi Jon, Would this be a similar feature request as the following: ? Thank you, Kat
Hi Chand, Thank you for reaching out. Can you please provide a link to the video you used to set up this Extractor? Running the code you provided, it appears there is an \ufeff in the Title key. This suggests there is a difference in the encoding. Can you please take a look at how your code Editor stores CSV files? Thank you, Kat
Hi Jatin, thank you for reaching out. This is not possible at the moment. What is your use case, or what type of metadata would you like to set?Best regards, Kat
Hi Shubham, thank you for reaching out.What source system are you connecting using the Cognite File Extractor? What type of filtering for the specific file would you like to perform? Would you like to filter by name, metadata information, or by file type?Best regards, Kat
Thank you for the reply - I will reach out to Pål. Can you please confirm if the original UI issue noted is still seen, or is this mitigated now?
Hi Erling, MQTT Support for the Hosted Extractors service will have a Beta release shortly. As such, the UI may have changed, or been updated to prepare for this release. Can you please go through the UI flow, and confirm if you still see this error? If you do, screenshots would be much appreciated, and helpful. At the moment, we are unable to recreate this error. Thank you, Kat
Hello @Erling Johannessen , The team has taken a closer look at this behaviour. Can you please confirm where you see this error, and what version of the Extractor you are using?In the recent versions of the UI, and the API, we were unable to re-create the issue. Thank you, Kat
Thank you for taking a look here!
Hi @Andreea Pastinaru , I have noticed this in the case where the external id I am hoping to exactly match on is also a prefix of many other external ids (say 100+). For example, if I hope to find an asset with external id WELL_, but I have many other assets with external ids where WELL_ is a prefix, I have difficulties finding the WELL_ asset in Fusion.
We use WITH clauses quite a lot when building up queries. However, when developing, I may want to investigate that sub table. I cannot do this with the preview button (which caps out at some runtime/some row limit). As such, I need to run the transformation on the full source tables to see the results of what I am building up. When running the transformation to view the quality of the transformation/an sub table, it needs to write to somewhere.
Already have an account? Login
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.
Sorry, our virus scanner detected that this file isn't safe to download.