Suggestion:
When reviewing an .ipynb file in Domo, there is a button to “Edit in Jupyter.” However, clicking this button does not reliably take the user back to the underlying code associated with that notebook.
In my case, I have an ipynb file named “US Map Geocode.ipynb.” There is no dataset with this name, yet the associated job is failing with an error indicating it cannot process. Because the Edit in Jupyter button does not clearly open or identify the correct notebook/code location, it is very difficult to determine which code is actually linked to the ipynb file that is failing.
Pain Points:
- The Edit in Jupyter button does not clearly return the user to the active code environment.
- There is no obvious way to identify which notebook or code object is linked to a given ipynb file.
- Debugging job failures becomes difficult when the dataset and notebook names do not align.
Suggested Improvements:
- Ensure the Edit in Jupyter button opens the exact notebook and code associated with the ipynb file.
- Provide clearer linkage or metadata showing which code/job is tied to an ipynb.
- Optionally display the notebook’s source or workspace path for easier troubleshooting.
This would significantly improve usability and reduce time spent debugging notebook-related job errors.
Thanks for considering this enhancement.
