Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
The .dtl option detail_circle_note_text when set to "DEFAULT" results in "SEE DETAIL" it can be set to another value such as "SEE VIEW" resulting in, you guessed it, SEE VIEW X attached to the leader. The problem is that the nomenclature attaced to the view itself will be DETAIL. The image below, courtesy of Steve C. Williams from PTC/User.org, illustrates the desired outcome.
The .dtl option view_note does not allow any customization. The only options available are std_ansi, std_iso, std_jis, std_din, std_gb & std_eskd. None of which will give the results shown below. To override the default you have to select the text, edit the properties and change the word "DETAIL" to "VIEW". My logic dictates that the settings should follow each other to be consistent, or the checker is going to let me know about it and besides I've got other things to do than change this every time I create a detailed view.
Don, Don't forget to vote on your idea!!!
I liked the image so much i voted just because it was in there.
and this one to automatically vote on your own request
Is there a typo in the first sentence?:
"The .dtl option detail_circle_note_text when set to "DEFAULT" results in "SEE DETAIL" it can be set to another value such as "SEE VIEW" resulting in, you guessed it, SEE DETAIL X attached to the leader. "
And this hasn't been reported and turned into an SPR?
And while we are at it, why are there 2 spaces between the statement and the value?
There is simply NO convention that calls for that.
Doug,
You're right it should have read "...you guessed it, SEE VIEW X attached to the leader..."
I thought so, otherwise it really didn't make sense. 😄
You should eb able to editit. Look for the "Edit Product Idea" link in the Actions menu on the upper right.