You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing a TXT_TABLE query in the GQL Sandbox, there are multiple ways in which to show the output:
This is a very useful feature, but the TXT_TABLE (as far as I know) doesn't allow any curves to be specified. Querying a curve however, does not have the same options:
If you want to validate a curve by doing some calculations in Excel, it is quite a hassle to properly export it. It would therefore be very useful if curves could be presented as CSVs in the GQL Sandbox.
@antw@noracato this is not an urgent issue but would be an awesome enhancement of the Sandbox. I'm not sure which one of you is best suited to pick this up, so feel free to re-assign. Notifying @marliekeverweij
The text was updated successfully, but these errors were encountered:
This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.
mabijkerk
added
Pinned
Will never be marked as stale or auto-closed.
and removed
Stale
Issue had no activity for 60 days and will be, or has been, closed.
labels
Nov 30, 2022
When writing a TXT_TABLE query in the GQL Sandbox, there are multiple ways in which to show the output:
This is a very useful feature, but the TXT_TABLE (as far as I know) doesn't allow any curves to be specified. Querying a curve however, does not have the same options:
If you want to validate a curve by doing some calculations in Excel, it is quite a hassle to properly export it. It would therefore be very useful if curves could be presented as CSVs in the GQL Sandbox.
@antw @noracato this is not an urgent issue but would be an awesome enhancement of the Sandbox. I'm not sure which one of you is best suited to pick this up, so feel free to re-assign. Notifying @marliekeverweij
The text was updated successfully, but these errors were encountered: