When I try to "add a resource" in adobe launch the previous revision and not latest revision I see this alert why? | Community
Skip to main content
Level 5
February 9, 2023
Solved

When I try to "add a resource" in adobe launch the previous revision and not latest revision I see this alert why?

  • February 9, 2023
  • 1 reply
  • 810 views

When I try to "add a resource" (A rule which is not latest revision but the previous revision) in adobe launch I see this alert why? But I can see the other library is using revision 23 but when I try to add a resource the same revision 23 it is showing an alert. 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jennifer_Dungan

Just to clarify... I assume you have a few libraries in your development area; and in one of those libraries you (or whoever is working on that build) is using revision 23?

 

You also want to use revision 23 in your build... but there is also a "latest" version... 

 

When you choose an older revision, it has to create and build a new revision, thus this will replace the existing "Latest" (this will create a new revision 24).

 

So if someone is actively working on that resource, you don't want to do that... it's a little annoying that you can't just use an older version... but by any chance is Revision 23 in prod right now? If so, you can just use the upstream version....

 

But really, you can't just load an older revision without building a new revision... I guess they assume that if you are choosing an older revision, there is something wrong with the newest revision... rather than just trying to deal with multiple development streams....

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
February 9, 2023

Just to clarify... I assume you have a few libraries in your development area; and in one of those libraries you (or whoever is working on that build) is using revision 23?

 

You also want to use revision 23 in your build... but there is also a "latest" version... 

 

When you choose an older revision, it has to create and build a new revision, thus this will replace the existing "Latest" (this will create a new revision 24).

 

So if someone is actively working on that resource, you don't want to do that... it's a little annoying that you can't just use an older version... but by any chance is Revision 23 in prod right now? If so, you can just use the upstream version....

 

But really, you can't just load an older revision without building a new revision... I guess they assume that if you are choosing an older revision, there is something wrong with the newest revision... rather than just trying to deal with multiple development streams....

aagk123Author
Level 5
February 15, 2023

Yes I tried to add the specific rule from another library to my library and in that library I could see the user had latest revision but was using older revision for some reason. So when I tried to add the older revision I saw this message.