Hi All,

I'm trying to publish and debug in my personal area from the debugger drop down menu and I get an error saying "1-Click Publish required - 'Procurement' was published with a different Service Studio version."  Any idea how to resolve this?


Thanks

Lalith

Hi

This message will appear when following reasons,

1) If you consumed any modules/reference, then you must publish first, then try Run and debug in personal area

2) Your version is not latest version in service center, the time working on some one will publish there version, what you need to do is, get there version and publish, after Run and debug in personal area.


So in your case do the publish and it will work in personal area.


Thanks,

Balu

Balu wrote:

Hi

This message will appear when following reasons,

1) If you consumed any modules/reference, then you must publish first, then try Run and debug in personal area

2) Your version is not latest version in service center, the time working on some one will publish there version, what you need to do is, get there version and publish, after Run and debug in personal area.


So in your case do the publish and it will work in personal area.


Thanks,

Balu


I have already published my module. Also, I clicked on Module > open another version,  and I see that my module is the latest version. I still have the error.

Thanks

Hi Lalith,

You should publish all your modules first using the latest Service Studio versions which you are using.
This could happen when you have some old modules published using previous Service Studio version and now you are using latest version of Service Studio for the debugging in personal environment.

Regards,
Palak Patel

Hi Lalith,

Try to publish all modules from latest version of service studio.

Thanks,

Rajat Agrawal


Thank for replying guys but as I have already said, I have published all of my modules with the latest service studio. I also tried creating a test application with a single module and tried to debug in personal area after publishing. This test app was only ever published with 1 service studio version, and I still get the same error. If it is relevant, I recently upgraded to outsystems 11 from outsystems 10.


Thanks

Lalith

Hi,


Is something like this?


I'm with this problem and I'm using SS11 Realease 2. What's your realease?


Best regards,

Ricardo

Ricardo Pereira wrote:

Hi,


Is something like this?


I'm with this problem and I'm using SS11 Realease 2. What's your realease?


Best regards,

Ricardo

Hi,

Yes, that is the same error. I'm using SS11 , development environment - 11.0.109.0


Thanks

Lalith


I think this can be a bug. 

Someone else have the same problem?

i do i can not debug in SS 11. I am using my free trial environement

Ran into this as well, don't really know why. Module has been created in the same version of Service Studio I'm using right now, even the same day I was not able to run in the personal environment. 


Any further ideas?

HI,

Analyse the debug mode on your administration of service center

Regards

Yeah that's turned on. It allows me to debug the published versions, but it won't let me run and debug in my personal area. Which is leading to many many unneeded versions as I change and debug little details. 

I solved this problem by 


1. Click F5 - One Click Publish

2. Click F6 _ Debug in Personal Environment

This bug was fixed in one of the updates of service studio. Just download lastest version and that should fix it.

We are on 11.7.4 Studio, and getting this error with an existing application already developed by some other team and we trying to debug. How to go about it ? Will publishing hurt in a negative way ? First of all we are not getting the 1 click publish enabled also .

Hello Nihar.


This topic is one year old. Maybe your problem deserves its own topic.

First, publishing has no negative impacts unless you broke something. If you can't publish, it's because when updating references you broke something. This means you need to really get some development done to be aligned with the rest of the environment that evolved in the meanwhile.

To debug you need the same version of Service Studio so I'm guessing it was developed a while ago and you haven't touched it since. Now is a good time to start.

Thanks Nuno. Yeah it would have been better if I had opened a new thread :-). At this point we are in a module which I see was published 2 days back , but still are there possibilities of getting this error ?


Yes. It can mean references where changed or Servcie Studio is in a differnet version. 

Can you talk with the developer that made those changes? Or compare with the version 3 days before ?

Ok. I just compared it with the latest published version and I get the message that there is no difference. Let me consult with the earlier team then.