Skip to main content
darkknight
darkknight
Expert ⭐️
December 16, 2021
New Idea

X-Org Needs improvement

  • December 16, 2021
  • 3 replies
  • 97 views

X-Org should be simplified and accommodate and support every field, asset and function in the tool - including new features at launch time.
 

Enterprise platform best practice is to build/test in a sandbox and promote to production. However - even though X-Org has come a long way - because of the gaps that still exist, the unreliable nature of the migrations (9 times out of 10 they inexplicably fail) and the fact that X-Org creates duplicate assets in the target org instead of changing the target asset, we still do 90% of our build directly in Production which increases chances of mistakes.
 

Also, X-Org considerations should be made whenever new features are being developed and released.  If X-Org cannot migrate it yet, it should not be released until X-Org can support it. 

    3 replies

    gunjanm
    gunjanm
    Expert ⭐️
    December 16, 2021

    Extremely well said. 

    Gunjan
      john.cowles
      john.cowles
      Helper ⭐️
      October 31, 2022

      We were really hoping the new x-org 2.0 would address some of our concerns, but unfortunately it didn’t address the biggest feature gap from our perspective.  While the new UI is better, it still doesn’t support updating objects like we think it should. 

      As mentioned in the original post here, enterprise grade applications have the ability to develop in a non-production environment and then migrate to production.  While x-org 2.0 can do some of this, it is not a one time event.  These objects may need to change because the Admin didn’t configure something correctly or maybe the design changed.  When this occurs, you need the ability to update the object.  

      The current approach of making a new copy of the object rather than updating it is not ideal and actually creates risk by forcing changes directly in production.  These objects are connected together and if you push a new object rather than an update, then you have to update the connected objects manually in production.  Not a great idea because of the risk.  

      Not having the ability to update objects really deflates the value of sandbox and creates risk for organizations that prefer to follow standard application development type lifecycles.  If this occurs, this can limit the willingness of an organization to grow the use of the application because that only increases risk in the current state.  

        shambhawi
        shambhawi
        Helper ⭐️
        December 8, 2022

        Hi @john.cowles, thanks for the great feedback.I am currently working as the product manger for X-org and we are working towards handling conflict resolution more gracefully with X-org tool.

        Will keep you posted  around the timeline by when this feature will be released.

          Terms & ConditionsAccessibility statement