is it mandatory to use export patch for changing object?

ShashankHNatesh (shashankn0001)
I agree with Mike Schmitt in that, it is the best way to export patch to higher environments.

And in answer to your question, if its "mandatory" ?

For lower environments, like development environments, you can go ahead and make changes to an object. When you want to bring this change to higher environments, what other options do you have other than creating a patch or patch application?

- You cannot export an object as such. Exporting the entire application, is not feasible since it is time consuming and undesirable. Also you will be importing changes of all other designers, whose development might not be complete.

- Also, directly editing the object on higher environments is forbidden , as it might override others changes, create incompatible versions and sometimes even break the code with improper testing.

The ideal way is to isolate your change , without disturbing other objects in an application, by adding it to a patch or through creating an application and adding your changed object to import it to higher environments. Even before you import your change, you should ensure that other designers work-in-progress changes on that object are not imported.

ShashankHNatesh (shashankn0001)
I agree with Mike Schmitt in that, it is the best way to export patch to higher environments.

And in answer to your question, if its "mandatory" ?

For lower environments, like development environments, you can go ahead and make changes to an object. When you want to bring this change to higher environments, what other options do you have other than creating a patch or patch application?

- You cannot export an object as such. Exporting the entire application, is not feasible since it is time consuming and undesirable. Also you will be importing changes of all other designers, whose development might not be complete.

- Also, directly editing the object on higher environments is forbidden , as it might override others changes, create incompatible versions and sometimes even break the code with improper testing.

The ideal way is to isolate your change , without disturbing other objects in an application, by adding it to a patch or through creating an application and adding your changed object to import it to higher environments. Even before you import your change, you should ensure that other designers work-in-progress changes on that object are not imported.