Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
  • Welcome
  • Products
  • Support
  • About
  • More
  • Cancel
OpenRoads | OpenSite
  • Product Communities
  • More
OpenRoads | OpenSite
OpenRoads | OpenSite Wiki Failed to Persist message when Exporting to Native
    • Sign in
    • -Road and Site Design - Wikis
      • +OpenRoads Designer
      • +OpenRoads ConceptStation
      • +OpenRail Designer
      • +OpenSite Designer
      • +OpenRoads Navigator Mobile App
      • -SS10/SS4/SS3 OpenRoads
        • Platform compatibility
        • +SS4/SS3 Subsurface Utilities Video Clips, TechNotes & FAQs
        • +3D Geometry (SS4)
        • +Analysis & Reporting (SS4)
        • +Basic Settings (SS4/SS10)
        • +Civil Cells (SS4)
        • +Corridor Modeling & Cross Sections (SS4)
        • geopakcom.exe - Entry Point Not Found - PowerGeopak Install Error in Windows 10
        • -General Geometry (SS4)
          • Change Color of Handlers and Manipulators
          • Context Tool Box does not appear for Geometry Elements
          • Curve Widening Table .wid file
          • Delete PI in OpenRoads (SS4)
          • Export Civil Geometry to MX - Halgn,Valgn and Verat Linemode
          • Failed to Persist message when Exporting to Native
          • Feature Not Displayed in 3D Model
          • General Geometry > Export to Native is not adding Verticals to Active Geometry Project
          • Graphic Manipulators Missing on Civil Elements
          • Horizontal Alignment Imported from Native into OpenRoads is Not Ruled
          • How can you delete Horizontal Geometry from OpenRoads? (SS4)
          • How do I create a copy of civil geometry? (SS4)
          • How to Export Corridor Modeling Elements to Native
          • How to set custom exaggeration values for the profile view
          • How to transfer geometry in an ALG file to a GPK file
          • How to use Associate MX Strings function
          • How to Use Create Civil Rule Feature Command
          • Import Geometry error after selecting GPK file "The specified module could not be found. (Exception from HRESULT: 0x8007007E)
          • Import InRoads ALG into OpenRoads (SS4)
          • Input MX geometry from an inp file to OpenRoads
          • Insert PI Into Civil Geometry in OpenRoads (SS4)
          • Key Station
          • Negative Co-ordinates
          • Profile does not export to GPK using Export to Native command or Auto Export in Feature Definition
          • Remove Snap Constraint
          • Two Point Line with Stationing does not show up as Chain in GPK file.
          • Unable to read file, Cannot find geometry importer dll
          • Vertical Alignment Imported from Native into OpenRoads is Not Ruled
          • Vertical Alignment is Not Exported to Native
          • Video : Civil Geometry Export to MX
          • Video : Create ICM
          • Video : Creating OpenRoads geometry and exporting the same to Native MX
          • Video : Difference between Deactivate Reference Rules & Remove Rules in Open Roads Technology
          • Video: How to Edit OpenRoads Stationing Symbology
          • Video: Alignment Annotation
          • Video: Apply Multiple Design Standards to a Single Complex Geometry Element
          • Video: Assigning a Feature Definition to Geometry
          • Video: Civil Geometry Import and Export
          • Video: Complex Transition Between Any Element and Arc - Example Workflow
          • +Video: Geometry Tools Overview
          • Video: How to Remove Civil Rule from Multiple Elements at One Time
          • Video: How to Set Element Information in Open Roads Technology
          • Video: Import Geometry and Changing Symbology/Feature Definition
          • Video: Import Native Geometry into OpenRoads
          • Video: Import Plan Graphics to OpenRoads
          • Video: Introduction to Civil Accudraw
          • Video: OpenRoads Integration with GPK File
          • Video: Reason and solution for element not valid for Tool error & Create Civil Rule Feature
          • Video: Ruling a Profile Imported from Native
          • Why Export to Native
        • +Horizontal Geometry (SS4)
        • +Rail Track (SS4)
        • ReadMe - What's new and revised in SS4 MR3 - Version 08.11.09.903+
        • +Survey (SS4)
        • +Terrain Model (SS4)
        • +Training for OpenRoads commands in InRoads/GEOPAK/MX SS4
        • +Vertical Geometry (SS4)
        • Visual Basic Run-time error '-2147467259 (80004005)' when loading GEOPAK through FDOT workspace
        • Why warning display Create an Unlinked Terrain Model
        • How to launch InRoads/GEOPAK SS10 from ProjectWise CONNECT
        • Print and Print to File Button Not Working
        • Problems Running SS4 VBA in SS10
      • +GEOPAK Native
      • +InRoads Native
      • +MX Native
      • +OpenRoads SignCAD

     
     Questions about this article, topic, or product? Click here. 

    Failed to Persist message when Exporting to Native

    Product(s): MX
    Version(s): 08.11.09+
    Area:  General Geometry
    Original Author: Jason Walsh, Bentley Technical Support Group

     

    Error Message:

    'Failed to Persist - check an active model has been selected' shows in Message Centre

    Solution 1: MX Model Changed:

    When an OpenRoads element has been Exported to Native (MX Model) additional information is stored in the OpenRoads element linking it to the native model.

    The image below is the Element information panel for a just created element.

    The image below is the Element information panel for the same element after it has been exported to native, this shows the MX model and string name now associated with this element.

    Changing the MX model from DESIGN IMPORT to DESIGN IMPORT 2 in the Feature Definition Toggle Bar as below and re-exported that element to native will display a Failed to Persist message.

    The Failed to Persist message appears due to the element already being linked to an MX model when it was originally exported to native.

    How to Resolve

    If you require the element to be exported to another MX model you can change the Model Name in the dropdown list of the Element information panel as below.

      

    This will move the element to that model. The Export to Native function will now work as the Feature Definition Toggle Bar has been set to match the MX model linked with the OpenRoads Element.

     

     

    Solution 2: MX String Removed:

    When the MX string linked with the OpenRoads Element has been deleted from the MX model the Failed to Persist message appears when re-exported to native.

    How to Resolve

    Select the element and go to the Element information panel. Click into the string name box.

    Hit the Enter key and this will re-create the string in the MX model. The Export to Native function will now work as a corresponding string now exists in the model to be updated.

     

    • native
    • Export
    • MX Model
    • Share
    • History
    • More
    • Cancel
    • Jason Walsh Created by Bentley Colleague Jason Walsh
    • When: Wed, Oct 1 2014 8:35 AM
    • Jacquelyn Pettus Last revision by Jacquelyn Pettus
    • When: Fri, Oct 17 2014 1:25 PM
    • Revisions: 6
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2021 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies