[vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n
[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n
Fixes<\/p>\n
[\/vc_column_text][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n
[\/vc_column_text][vc_column_text]<\/p>\n
Fixes<\/p>\n
[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n
[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n
Enhancements<\/p>\n
Fixes<\/p>\n
Fixed an issue when modifying existing conditions for circumstances where the ‘Use Gross Area’ setting is untoggled to be handled accurately.<\/span><\/p>\n<\/li>\n<\/ul>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n Fixes<\/p>\n Fixed a reporting accuracy issue for local comparison results when a key measure is produced by multiple conditions across multiple Revit categories.<\/span><\/p>\n<\/li>\n<\/ul>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n Fixes<\/p>\n Revised Pipeline exports for locally run comparison groups to align with Pipeline data structure and processing needs. Additionally, a new validation check for comparison group setup will help users determine if a selected option for the comparison group is contained within the selected import configuration for LotSpec option sets.<\/span><\/p>\n<\/li>\n<\/ul>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n Fixes<\/p>\n Pipeline Connect has been republished to support minor changes made to LotSpec for Revit 23.3. Customers using LotSpec for Revit 23.3 are advised to upgrade Pipeline Connect to 23.3.2 to ensure proper compatibility with one another.<\/span><\/p>\n<\/li>\n<\/ul>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n Fixes<\/p>\n Fixed an issue when solving LotSpec option sets where if the project is not linked to a Pipeline asset, the project will fail to create the \u201cpending\u201d files and database if auto upload is turned off.<\/p>\n<\/li>\n<\/ul>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column width=”2\/3″][vc_column_text]<\/p>\n New Feature<\/p>\n Key measure comparisons for LotSpec for Revit option sets can now be processed and reviewed locally<\/i> within Revit which no longer requires Pipeline estimating to be part of this process. Processed comparisons will show only what is different<\/em> as opposed to retaining redundant common quantities resulting in up to 80% data size reduction and will significantly streamline the file handling performance when working with Pipeline estimating. Locally created comparison groups are now stored within the project.[\/vc_column_text][\/vc_column][vc_column width=”1\/3″][vc_empty_space height=”92px”][vc_single_image image=”11630″ img_size=”full” onclick=”link_image”][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n Fixes<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n New Features<\/p>\n A Multi-House Setup feature has been created to support API connected workflows where a single Revit project needs to drive material changes for multiple<\/em> Pipeline houses with greater efficiently. This could be useful for organizational strategies where spec level or high impact divisional variations (like foundation types) are broken into multiple Pipeline houses but still related to a single plan.[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n Enhancements<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n Enhancements<\/p>\n Fixes<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n New<\/p>\n The X-RAY application has been renamed to “Pipeline Connect<\/strong>\u201d in an effort to provide stronger single word clarity as to what this applications role and place is in our Pipeline ecosystem today. Built primarily to serve our Pipeline estimating platform, Pipeline Connect<\/strong> allows Autodesk\u00ae Revit\u00ae users to connect<\/em> their projects and quantities to Pipeline assets to facilitate a more dynamic BIM sourced estimating workflow.<\/p>\n Over the past year, we\u2019ve worked diligently to add features that will allow our Revit users to work more efficiently with Pipeline via a Pipeline connected <\/em>workflow and with the addition of the following recent capabilities, hope you’ll agree that the name change makes sense.<\/p>\n With release 23.0 and beyond, the full product name will now be referred to as Pipeline Connect <\/strong>for Autodesk\u00ae Revit\u00ae. The functionality and resources available for this application for any supported version still remain the same<\/u>, however you will notice some minor updates have occurred on our help site to accommodate the name change. The xray.support@strongtie.com<\/a> email will continue to remain in service for some time however we are now directing our users to use pipeline.support@strongtie.com<\/a><\/strong> so that all Pipeline ecosystem products can be handled together.[\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_separator][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text]<\/p>\n Enhancements<\/p>\n [\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n","protected":false},"excerpt":{"rendered":"[vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text] Pipeline Connect version 2023.4.2 Released – 11\/19\/2024 [\/vc_column_text][\/vc_column][\/vc_row][vc_row row_type=”row” stretch_row_type=”no”][vc_column][vc_column_text] Fixes Fixed an issue where the delta comparison did not correctly display the option list after reopening the dialog during the Pipeline upload process. Fixed an issue with the delta comparison to ensure accurate results when key measure IDs span multiple Revit […]","protected":false},"author":44,"featured_media":0,"parent":705,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"template-page-full-width.php","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-11417","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/help.strongtietech.com\/pipelinerevit\/wp-json\/wp\/v2\/pages\/11417","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.strongtietech.com\/pipelinerevit\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/help.strongtietech.com\/pipelinerevit\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/help.strongtietech.com\/pipelinerevit\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/help.strongtietech.com\/pipelinerevit\/wp-json\/wp\/v2\/comments?post=11417"}],"version-history":[{"count":0,"href":"https:\/\/help.strongtietech.com\/pipelinerevit\/wp-json\/wp\/v2\/pages\/11417\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/help.strongtietech.com\/pipelinerevit\/wp-json\/wp\/v2\/pages\/705"}],"wp:attachment":[{"href":"https:\/\/help.strongtietech.com\/pipelinerevit\/wp-json\/wp\/v2\/media?parent=11417"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Pipeline Connect version 2023.3.<\/strong>4<\/strong><\/a><\/h1>\n
Released – 3\/11\/2024<\/h4>\n
\n
Pipeline Connect version 2023.3.<\/strong>3<\/strong><\/a><\/h1>\n
Released – 1\/19\/2024<\/h4>\n
\n
Pipeline Connect version 2023.3.2<\/strong><\/a><\/h1>\n
Released – 11\/27\/2023<\/h4>\n
\n
Pipeline Connect version 2023.3.1<\/strong><\/h1>\n
Released – 9\/29\/2023<\/h4>\n
\n
Pipeline Connect version 2023.3.0<\/strong><\/h1>\n
Released – 9\/18\/2023<\/h4>\n
Local Key Measure Comparison Processing<\/strong><\/h4>\n
Pipeline Connect version 2023.2.1<\/strong><\/h1>\n
Release Date – 5\/15\/2023<\/h4>\n
\n
Pipeline Connect version 2023.2<\/strong><\/h1>\n
Released – 5\/8\/2023<\/h4>\n
Multi-House Connected Workflow<\/strong><\/a><\/h4>\n
\n
Pipeline Connect version 2023.1<\/strong><\/h1>\n
Released – 12\/12\/2022<\/h4>\n
\n
\n
Pipeline Connect version 2023.0<\/strong><\/h1>\n
Released – 6\/6\/2022<\/h4>\n
Hello “Pipeline Connect<\/strong>“<\/h4>\n
\n
\n