{"id":4491,"date":"2016-07-11T13:58:43","date_gmt":"2016-07-11T12:58:43","guid":{"rendered":"http:\/\/www.solidapps.co.uk\/blog\/?p=4491"},"modified":"2016-07-11T13:58:43","modified_gmt":"2016-07-11T12:58:43","slug":"why-is-the-flat-pattern-drawing-view-out-of-synch-with-the-part","status":"publish","type":"post","link":"https:\/\/www.solidapps.co.uk\/blog\/2016\/07\/why-is-the-flat-pattern-drawing-view-out-of-synch-with-the-part\/","title":{"rendered":"Why is the flat pattern drawing view out of synch with the part?"},"content":{"rendered":"<p>Users often ask: why \u2013at times \u2014 did the flat pattern drawing view not update\u00a0after changing the part?\u00a0 First, let us recall that flat pattern drawing views are created from a flatten derived configuration. When you create\u00a0a flat pattern drawing view, the system automatically creates a flatten derived configuration (Fig. 1)<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-12111 colorbox-12110\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig1-2-615x206.png\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" srcset=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig1-2-615x206.png 615w, http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig1-2-300x101.png 300w, http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig1-2.png 638w\" alt=\"Fig1\" width=\"615\" height=\"206\" \/><\/p>\n<p>This means that there could be circumstances where the default and derived configurations are out of sync with each other.<\/p>\n<p>For example, in Fig.2\u00a0 you can see that the part length in the isometric view is 200 mm, while the flat pattern drawing view is showing the same part with a 100 mm in length.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-12113 colorbox-12110\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig2-3-615x350.png\" sizes=\"auto, (max-width: 615px) 100vw, 615px\" srcset=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig2-3-615x350.png 615w, http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig2-3-300x171.png 300w, http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig2-3.png 647w\" alt=\"Fig2\" width=\"615\" height=\"350\" \/><\/p>\n<p>In order to understand why there could be circumstances in which this issue happens, we need to move it out of the sheet metal context and explain how derived configurations work in general.<\/p>\n<p>This situation usually happens when a feature in the part is in the contexts of an assembly. The most typical situations are the following:<\/p>\n<p>1) A component feature uses an assembly sketch as a reference<br \/>\n2) A component feature uses a component sketch as a reference<br \/>\n3) A component feature uses a component entity as a reference.<\/p>\n<p>In Fig.3 we see an assembly component and an assembly sketch. You set the component boss-extrude feature with an up-to-vertex end condition using as a \u201cvertex\u201d the assembly sketch endpoint.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-12115 colorbox-12110\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig3-3.png\" sizes=\"auto, (max-width: 577px) 100vw, 577px\" srcset=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig3-3.png 577w, http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig3-3-300x194.png 300w\" alt=\"Fig3\" width=\"577\" height=\"373\" \/><\/p>\n<p>This means the component boss-extrude feature length is controlled by the length of the assembly sketch. While working in the assembly you change the length of the assembly sketch, the default configuration updates on rebuild (Fig. 4.)<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-12116 colorbox-12110\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig4-2.png\" sizes=\"auto, (max-width: 489px) 100vw, 489px\" srcset=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig4-2.png 489w, http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig4-2-300x167.png 300w\" alt=\"Fig4\" width=\"489\" height=\"273\" \/><\/p>\n<p>If at this point you save and close the assembly and then open the part again by itself, the default configuration had updated while performing the operation in the assembly.<br \/>\nHowever, if you activate the derived configuration, you will see that the extrude has not updated. The reason is that the derived configuration does not have the \u201cexternal reference\u201d information to update. It needs the assembly to update. The part only stores the path to the external reference or assembly. As we can see in Fig.5 the in-context Boss-Extrude2 is out-of-context<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-12117 colorbox-12110\" src=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig5-1.png\" sizes=\"auto, (max-width: 499px) 100vw, 499px\" srcset=\"http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig5-1.png 499w, http:\/\/blogs.solidworks.com\/tech\/wp-content\/uploads\/sites\/4\/Fig5-1-300x161.png 300w\" alt=\"Fig5\" width=\"499\" height=\"267\" \/><\/p>\n<p>This same principle applies to the flat pattern drawing view. If you created a part using an in-context feature, and this feature changes, make sure you update the derived configuration before you close the assembly.<\/p>\n<p>Originally posted in the <a href=\"http:\/\/blogs.solidworks.com\/tech\/2016\/05\/flat-pattern-drawing-view-synch-part.html\" target=\"_blank\">SOLIDWORKS Tech Blog<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Users often ask: why \u2013at times \u2014 did the flat pattern drawing view not update\u00a0after changing the part?\u00a0 First, let us recall that flat pattern drawing views are created from&hellip; <\/p>\n","protected":false},"author":1,"featured_media":4492,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[25],"class_list":["post-4491","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-solidworks","tag-solidworks-2"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/4491","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=4491"}],"version-history":[{"count":1,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/4491\/revisions"}],"predecessor-version":[{"id":4493,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/posts\/4491\/revisions\/4493"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/media\/4492"}],"wp:attachment":[{"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=4491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=4491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.solidapps.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=4491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}