Abinitio EME

In my sandbox i am having 10 graphs, i checked-in those graphs into EME. Again i checked-out the graph and i do the modifications, i found out the modifications was wrong. what i have to do if i want to get the original graph..?

Questions by shylender

Showing Answers 1 - 22 of 22 Answers


  • Mar 3rd, 2008

Here is my understanding of your problem:

Say your orginal version number of the graph is "100" and after you made the first set of modification and checked in, the graph gets a version of, say "102".
Now you checked out the latest version of the graph, i.e. version 102 and did another set of modifications. After checking in (say new version number 105) you realise that the changes were incorrect.

In such a case the correct version is 102 on which you have to make the second set of changes again.

To achieve this, check out version 102 (select appropriate version number in check-out wizard), check it in again without any modification and setting the "force overwrite" option on. This will create a new version of the graph, say 108, and this version will be the same as version 102.

So now you have version 102 as the latest version with a new version number 108, you can lock and make the correct modifications on it.

Another way is to branch out, but in your scenario it doesn't appear to be the right option.

I have used version numbers in the explanation, which can be replaced by "tag names".


  • May 11th, 2008

After you realise that your chage is wrong, press unlock button, save the changes in other file name. Checkout again the same graph with correct version.

Best practice

1. Checkout all the graphs from a project to the corresponding sandbox
2. Checkin only the changed graph.

  Was this answer useful?  Yes

You can acheive this by using the concept of tags in abinitio. You check out a graph with tag name later when you don't want the modifications and you wish to revert back to the original version you can acheive this.

Hope this helps,

  Was this answer useful?  Yes

According to your problem statement, all the 10 graphs that you checked in into the EME get stored there as the latest graphs with the latest tag. This thing also reflects in your current latest sandbox. As you checked out and modified the graph by locking it in your own sandbox, and found that the modifications were not correct, you can simply follow this simple approach. Dont checking anything into the EME. Just re-checkout the graph from the EME (which is actually unaffected by your modifications) over the modified graph in your sandbox. This will sort of overwrite the unmodified graph (which you want) over the unwanted modified graph. This solves your problem.

  Was this answer useful?  Yes

The above answers stays valid if you did not checked in again after making the modifications. As the modifications are saved in sandbox there is always a revert back option by checkout to the previous version of the graph from EME to sandbox.

Abhisek B
fresh as dew!!

  Was this answer useful?  Yes

I agreed to above explanations. However if I didnt used a TAG while checking in the version which I want to checkout later on then well in that case what we can do? Any suggestions?

  Was this answer useful?  Yes


  • Dec 13th, 2011

Could we check out using the version number?

  Was this answer useful?  Yes


  • Feb 6th, 2012

Check Out from older version which is the correct one and check it in again. Make sure of using correct version number while checking out.

  Was this answer useful?  Yes


  • Nov 22nd, 2012

If you are not tagged the older version object (102).. and still you want to checkout the older version, than create a tag for the older version (102) by using r-tag option and do a checkout.

  Was this answer useful?  Yes


  • Dec 3rd, 2014


  Was this answer useful?  Yes


  • Mar 31st, 2015

Check Out again

  Was this answer useful?  Yes


  • May 30th, 2016

Find the object using air object versions and then checkout the version.
If you get a "cannot checkout" from Coop then use -force option.

  Was this answer useful?  Yes


  • May 31st, 2016

If locked and modified the graph. Unlock it and revert the changes or checkout again

  Was this answer useful?  Yes

Shikhar Singh

  • Jun 1st, 2016

Ideally a tag should be created with every checkin by the user. So in that case do a "tag Specific checkout" for the older code to reflect out in your SB. In case of conflicts ( which happens due to SB and REPO not in sync , you can do a force checkout)
The command will be "air project export" . You may want to have a dry run before .

  Was this answer useful?  Yes

Ayon Hazra

  • Jun 29th, 2017

First find the version of the object using air object version command, then run a backend checkout command which should have -version option to checkout correct version of the object.

  Was this answer useful?  Yes

Jatin Chawla

  • Sep 20th, 2020

air object rollback to rollback to previous version

  Was this answer useful?  Yes


  • Jan 9th, 2021

Do revert changes...
Another option is to checked out previous version of object from eme

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions