Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Keyboard shortcut for refresh CBOM - a lot of wasted mouse movement time
Having a keyboard shortcut for CBOM refresh would be great, moving from assembly to assembly and part to part you are forever refreshing the CBOM with the button top right. Having the ability to map a keyboard shortcut to this would be great.
I think better than a hotkey for refresh it would be nicer if the number of times you have to refresh the cBOM is cut down.
If I'm in a parent assembly, I can do a full refresh and get all the cBOM for all subassemblies. Then I open one of the subassemblies and have to refresh again. Then I open a child part and have to refresh again. Then I go back to the parent assembly and have to refresh yet again. Why? No new information was gained after the first refresh and yet I've had to wait for 4 refreshes at that point.
The info in the first refresh should just be cached locally and automatically pulled into the cBOM view if it exists. There should be some indication of when the last time a refresh occurred and some kind of condition that marks the cached cBOM as stale, preventing certain types of actions if it's old information (but you should still be able to see all the information you have cached, run a search on the cBOM, etc). To be honest though, I am not aware of anything that currently prevents me from refreshing the cBOM, walking away for a couple hours and then coming back to interact with the cBOM, so maybe they already have ways to deal with outdated cBOM info. Anyway, in the current state we're just wasting time and bandwidth to request the exact same information from the Upchain server multiple times.
@imckenzieY7CGY I fully agree, when you start counting up each team member and the amount of refreshing going on the wasted downtime multiplies very quickly. It may only seem a few secs or min at the time but add that up for a full day --> week --> year. At a guess, you could easily quantify a full work week of downtime just on refreshing alone (dependent on team size of course).
