Skip to main content
March 11, 2022
Solved

why we will get dependents errors during exporting an application why not precedent error??

  • March 11, 2022
  • 3 replies
  • 0 views

dependent and precedent errors in exporting application

    Best answer by andrewh0007

    If you move an object into a new environment that is dependent on another item that doesn't exist then it will fail, you can't reference something that doesn't exist in the target environment.

    If a precedent isn't in the new environment then nothing fails as nothing in the new environment is trying to reference something that isn't in that environment.

    I'm a little confused by the question though so I may be misunderstanding what you're asking. Why would you want precedent errors?

    3 replies

    andrewh0007
    March 11, 2022

    If you move an object into a new environment that is dependent on another item that doesn't exist then it will fail, you can't reference something that doesn't exist in the target environment.

    If a precedent isn't in the new environment then nothing fails as nothing in the new environment is trying to reference something that isn't in that environment.

    I'm a little confused by the question though so I may be misunderstanding what you're asking. Why would you want precedent errors?

    March 11, 2022

    thank you  

    to clarify why only dependent errors  occured.

    March 11, 2022

    We get missing precedent error/warning while exporting application if a required object is not included in the package and not already in the target environment.