| Author |
Share Topic Topic Search Topic Options
|
kimj
IdeaBlade
Joined: 09-May-2007
Posts: 1391
|
Post Options
Quote Reply
Topic: Ignoring warnings treated as errors Posted: 28-Dec-2012 at 3:43pm |
|
Great! Thanks for the update.
|
 |
stephenmcd1
DevForce MVP
Joined: 27-Oct-2009
Location: Los Angeles, CA
Posts: 166
|
Post Options
Quote Reply
Posted: 28-Dec-2012 at 3:08pm |
|
Just wanted to finish out this thread by mentioning that all the issues we were seeing with warnings going away have been fixed in 6.1.11. Thanks!
|
 |
stephenmcd1
DevForce MVP
Joined: 27-Oct-2009
Location: Los Angeles, CA
Posts: 166
|
Post Options
Quote Reply
Posted: 30-Nov-2012 at 1:30pm |
Thanks so much. That will help us out. And I'll just have to hope that some of the other issues we are seeing (like this one or this one) will also make it into that release.
|
 |
DenisK
IdeaBlade
Joined: 25-Aug-2010
Posts: 715
|
Post Options
Quote Reply
Posted: 30-Nov-2012 at 11:51am |
|
We expect to have the 6.1.10 patch release sometime next week.
|
 |
stephenmcd1
DevForce MVP
Joined: 27-Oct-2009
Location: Los Angeles, CA
Posts: 166
|
Post Options
Quote Reply
Posted: 28-Nov-2012 at 1:15pm |
That is great news. The behavior you describe sounds exactly like what we are looking for. Any estimates on just how much "sooner" the 6.1.10 release would be? Thanks!
|
 |
DenisK
IdeaBlade
Joined: 25-Aug-2010
Posts: 715
|
Post Options
Quote Reply
Posted: 28-Nov-2012 at 12:14pm |
Hi Stephen,
We have decided to release 6.1.10 sooner.
Just to clarify, the fix is to keep all client validation errors before and after save instead of clearing them. With this fix, you'll be able to keep your warnings after the save comes back from the server. The only difference with the old behavior is that, under the covers, we used to ship the client errors as well to the server, but now, we don't.
Please let me know if any of these is unclear for you.
|
 |
stephenmcd1
DevForce MVP
Joined: 27-Oct-2009
Location: Los Angeles, CA
Posts: 166
|
Post Options
Quote Reply
Posted: 27-Nov-2012 at 1:58pm |
|
That is a long time to wait. We are coming up on a big code freeze for our application towards the end of December so mid January would be too late for us to be taking a new version of DevForce. Would there be any way to maybe get a minor new release sooner than then? Something like a 6.1.9.1?
|
 |
DenisK
IdeaBlade
Joined: 25-Aug-2010
Posts: 715
|
Post Options
Quote Reply
Posted: 27-Nov-2012 at 11:55am |
Hi Stephen,
We're planning to schedule our next release sometime in mid January. Please let me know if this doesn't work for you.
|
 |
DenisK
IdeaBlade
Joined: 25-Aug-2010
Posts: 715
|
Post Options
Quote Reply
Posted: 27-Nov-2012 at 8:45am |
|
The fix is now available but I still don't have a date yet for the next official release. Let me find out and get back to you as soon as possible.
|
 |
stephenmcd1
DevForce MVP
Joined: 27-Oct-2009
Location: Los Angeles, CA
Posts: 166
|
Post Options
Quote Reply
Posted: 21-Nov-2012 at 1:57pm |
I know you mentioned a possible workaround....we didn't go down that road because we assumed an official fix would be coming soon. If the fix can make it into an official release soon, I think we can continue to wait a bit longer. When do you think the fix would be available?
Thanks.
|
 |
DenisK
IdeaBlade
Joined: 25-Aug-2010
Posts: 715
|
Post Options
Quote Reply
Posted: 21-Nov-2012 at 1:03pm |
Hi Stephen,
We apologize. We missed this bug when releasing 6.1.9. I've put this on a very high priority and asked our lead developer to take a look at it as soon as possible. Please let us know if this issue is blocking you.
Thank you for your patience.
|
 |
stephenmcd1
DevForce MVP
Joined: 27-Oct-2009
Location: Los Angeles, CA
Posts: 166
|
Post Options
Quote Reply
Posted: 20-Nov-2012 at 10:57am |
Originally posted by DenisK
The official fix will be in 6.1.9 however we currently have not scheduled it yet. |
Did the fix for this make it in to 6.1.9.0? We just upgraded our application but are still seeing the validations go away after a save.
|
 |
stephenmcd1
DevForce MVP
Joined: 27-Oct-2009
Location: Los Angeles, CA
Posts: 166
|
Post Options
Quote Reply
Posted: 26-Jul-2012 at 2:23pm |
|
Great, thanks for the update. I'm sure that will be fine for us. If not, I will let you know (or maybe just go with the workaround). Thanks!
|
 |
DenisK
IdeaBlade
Joined: 25-Aug-2010
Posts: 715
|
Post Options
Quote Reply
Posted: 26-Jul-2012 at 12:02pm |
The official fix will be in 6.1.9 however we currently have not scheduled it yet.
Please let me know should this issue become troublesome for you.
|
 |
stephenmcd1
DevForce MVP
Joined: 27-Oct-2009
Location: Los Angeles, CA
Posts: 166
|
Post Options
Quote Reply
Posted: 25-Jul-2012 at 2:23pm |
Thanks for the confirmation. Currently, we hadn't attempted any work arounds. Our app isn't in production just yet so this is something that we can live with for the moment.
Storing and then restoring the warnings during save seems doable. Any idea when an official fix would make it's way in to DevForce? If the fix will come in the next version, we might be able to just wait. Otherwise, we can look into the temporary workaround you suggested.
Thanks!
|
 |
DenisK
IdeaBlade
Joined: 25-Aug-2010
Posts: 715
|
Post Options
Quote Reply
Posted: 25-Jul-2012 at 12:26pm |
Hi Stephen,
You are correct. This is unfortunately a bug in that new IgnoreClientValidationErrors flag logic and breaks the Warnings verifier behavior you described above. I will open a bug report.
If you haven't yet found one, a workaround that I can only think of is to keep track of the Warnings prior to save in a separate collection, such that when the client save is done, you can add back the Warnings. But I hope you already found a better workaround. Please let me know.
|
 |