In Data Lineage, previously you could open a dataset in the preview window, view the data, click on a cell, hit Ctrl/Command+C to copy the contents of that cell. Why then did that change in the last few days to copy the RID for the selected resource? This now is the same functionality in pipeline builder’s preview window and it is incredibly frustrating and slows me down (as I can preform this operation 10’s or 100’s of times per day), to now I have to right click and click on copy to copy the cell contents.
Why was this change made and can it possibly be reverted? Who was asking for this change?
This change was introduced as part of a larger effort to make it possible to copy the contents of one application to another easily. We have received several requests related to improving this, either for copying the contents of one Data Lineage graph to another, or copying from Data Lineage to another application.
I have pushed a hotfix to correct this issue such that the copy hotkey only applies to the contents of the graph if your last interaction (click or drag) was on the graph. If your last interaction was with the table, then the copy hotkey should apply to the contents of the table. This hotfix also applies to Pipeline Builder. Assuming you are using the latest release of the application, this hotfix will be available to you within a day. I think you can check if you are on the latest release by clicking the “?” icon in the left sidebar, then clicking the “About” menu option. If the version listed in that dialog is 6.430 or later, then this hotfix will arrive soon.
I understand that this was frustrating to deal with, but I would encourage a less dramatic tone in the future. We are doing our best to make improvements to the product without causing regressions, but due to the complexity of some of our interfaces, it’s not always possible to catch every issue that might arise. The development team receives every request posted on this website, and we try our best to work quickly to resolve major issues. We appreciate your patience.
Wow, thank you for the quick response and action on this! Unfortunately not all the issues I’ve reported over the years on various stacks get responded to quickly, this is definitely appreciated. And changing to the platform version to Beta has the hotfix! A great use of the platform version feature!
I’m sorry my tone came off dramatic. I do quite enjoy working in Foundry and there are so many positive aspects of the platform. But there has been a consistent history of Palantir changing aspects of Foundry with 0 communication to end users, at least a few times a year, that cause negative impacts to QOL or feature support. The release notes and announcements have been a welcome addition. One great improvement in change management are the alerts in Data Lineage, communicating the upcoming change to the hotkeys! These are all great movements in the right direction, but there are still times that changes occur with no warning/communication, and it is uncertain if the issue will be deemed major and receive attention (like Workshop silently changing the time zone of a timestamp from a Function to the user’s local time, with no option to disable it). To be honest, I didn’t think this wouldn’t get the quick response it did. But I will work on conveying issues/bugs in a less dramatic tone, but I will continue to report the impact of issues/bugs, so the scope of the issue/bug is known.