{"id":102,"date":"2011-10-06T04:57:43","date_gmt":"2011-10-06T04:57:43","guid":{"rendered":"https:\/\/www.xrev.com.au\/news\/?p=102"},"modified":"2012-03-16T05:01:12","modified_gmt":"2012-03-16T05:01:12","slug":"xrev-transmit-build-1-2-10","status":"publish","type":"post","link":"https:\/\/www.xrev.com.au\/news\/xrev-transmit-build-1-2-10\/","title":{"rendered":"Xrev Transmit &#8211; Build 1.2.10"},"content":{"rendered":"<p><strong>We&#8217;ve recently addressed a few minor issues:<\/strong><\/p>\n<ul>\n<li>When adding Xrev Transmit &#8211; Issue command to the quick access toolbar there was no logo,<\/li>\n<li>&#8220;Issue Name&#8221; was not substituting when doing an &#8220;Untracked Issue&#8221;<\/li>\n<li>Added the &#8220;Issue Reason&#8221; to the summary tab of an &#8220;Untracked issue&#8221;<\/li>\n<li>A sheet may not show when doing an appended transmittal if you started a new project, setup the sheets, then saved as for another building and renumbered the same sheets to be non-duplicates. \u00a0This was because internally we were tracking the sheets by their unique ID. \u00a0Using Save as does not reset the ID&#8217;s so this meant that it was possible to have two sheets in different files with different sheet numbers but with the same &#8220;Unique ID&#8221;. \u00a0As such, certain sheets may not show up in your transmittal because Xrev Transmit thought it was already entered.<\/li>\n<\/ul>\n<p>We believe we have addressed all outstanding bugs (with the exception of certain dodgy printer drivers\/printer permissions that can cause the Revit API to play up). \u00a0If you do experience any issues please don&#8217;t hesitate to report them to us as we consider all bug fixes as priority 1.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We&#8217;ve recently addressed a few minor issues: When adding Xrev Transmit &#8211; Issue command to the quick access toolbar there was no logo, &#8220;Issue Name&#8221; was not substituting when doing an &#8220;Untracked Issue&#8221; Added the &#8220;Issue Reason&#8221; to the summary &hellip; <a href=\"https:\/\/www.xrev.com.au\/news\/xrev-transmit-build-1-2-10\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,4],"tags":[],"class_list":["post-102","post","type-post","status-publish","format-standard","hentry","category-bug-fixes","category-new-release"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/posts\/102","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/comments?post=102"}],"version-history":[{"count":0,"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/posts\/102\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/media?parent=102"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/categories?post=102"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.xrev.com.au\/news\/wp-json\/wp\/v2\/tags?post=102"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}