Table MBO's in v9.1.3

Kal Enika

Hi,

 

We recently upgraded to 9.1.3 and all of our table MBO's that have parameters suddenly stopped working. We are getting the following error:

 

Exception 'Must declare the scalar variable "@FolderID".' occurred when attempting to 'MBO update'.

 

Any ideas or anyone run in to the same issue?

 

Thanks!

-Kal

Kal Enika

Update:

 

Metastorm helpdesk has identified this as a bug in 9.1.3 and escalated it to development..

 

Brian Mellert

Glad I waited.  I am a bit gun shy after the issues with 9.1.2.  Making me want to wait a while or until 9.1.#.1 comes out at least.  Thanks for letting us know.

Paul_York

That's a pretty big thing to miss during testing!

achopra

Table BO's with parameters seem to be working fine for me in 9.1.3.  Are there specific environmental factors in play perhaps?

 

I am running on Win2008 64-bit with a SQL 2008 database.  My test BO connects to the Metastorm repository.

DSmith

I also am encountering this issue, but it seems to be isolated to one of the procedures I converted from version 7, at least thus far. Exact same message Details:Exception 'Must declare the scalar variable "@myFolderIDT".' occurred when attempting to 'MBO update'. and this was running on 9.1.2. the behavior happens on editable grids after you add a record when you try to commit the form back to the DB, you get treated to this message. Support says that it effects update, delete and add and will require a hotfix. I also am seeing a problem with client designers connecting to the deployment server. It should be noted that some chages were made in IIS and a few of the Appplication pools upgraded from .NET 2.0 to 4.0 in this release which brought on some security issues, mostly surrounding Network Service access to the machine.config file in c:\windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config As far as configuration I am also running on a 64 bit 2008 server with a SQL 2005 db.

Sean Mao

We are also using Win2k8 64bit and sql 2008. this problem occurs when you try to update a table MBO. The parameter works fine for reading data but won't update on submit.

Jerome_Pearce

Tested a while ago, but forgot to update here. We have the same problem immediately when using an edit grid of any kind.

 

I also agree that the level of testing should be elevated to include such things as a regular regression test case. Unfortunately I recommend never installing a SR release until either no faults have been reported for some time, or it gets to hotfix 2. I would love it if this were not so.

John Newman

Kal,  did you find a workaround?

Kalyan Enika

Nope.

I just went back to using Query MBO's and used the classic "Add/Update/Delete" buttons.

John Newman

I talked with Metastorm support and they said that the 9.1.3.1 hotfix will be released by the end of the month (today). The hotfix will address this issue. Hopefully, they are on schedule with this release.

Brian Mellert

I just read the release notes for 9.1.3.1 (announced elsewhere on this site).  It doesn't mention MBOs, unless it listed as something else or I'm missing it completely.  (Both possible.)

achopra

I forwarded this thread along to development...they are telling me that it was indeed fixed in 9.1.3.1.  I am not sure why it wouldn't be in the release notes though, and I haven't had a chance to test it personallly.  Can someone run a quick test to see if it works now?

Grzegorz Lag

At this stage 9.1.3 is useless. ////

Grzegorz Lag

It looks like it works in 9.1.3.2

Graham Field

This also affects a BO query where a parameter is used more than once. Here is an example query that allows optional parameters without causing table scans.

 

SELECT  Top 200  ClientId, ClientName, address, Location, OriginatorFE, OpenedOn, clStatus, cloc
FROM         vwClientDetail (NoLock)
Where ClientName Like IsNull(@ClientName,'') + '%'
And ((IsNull(@ClientId,'') = '') or (ClientID like '%' + @ClientId ) )
And ((IsNull(@Location,'') = '') or (cloc = @Location))
And (Isnull(@Search,'') = 'Yes')
Order by ClientName   

 

I've retested in 9.1.3.2 and although I reported this as a fault in 9.1.3, it's still not working. I've sent an email to Metastorm to escalate the issue. The above query works fine in 9.1.2

 

Graham

Robert Vignerot

Graham,

 

I believe this is a different issue to the one with Table Business Objects previously described.  The issue you are encountering is something to do with a change in the implementation of parameters in Query Business Object.  Evidently, you can no longer use the same parameter twice within the query!  I'm not exactly sure why this is the case, but it is really annoying to me. 

 

However, you can work around the issue by changing this to be:

 

SELECT  Top 200  ClientId, ClientName, address, Location, OriginatorFE, OpenedOn, clStatus, cloc

FROM         vwClientDetail (NoLock)

Where ClientName Like IsNull(@ClientName,'') + '%'

And ((IsNull(@ClientId1,'') = '') or (ClientID like '%' + @ClientId2 ) )

And ((IsNull(@Location1,'') = '') or (cloc = @Location2))

And (Isnull(@Search,'') = 'Yes')

Order by ClientName

 

As I said, freaking annoying!  But it does work.  Of course, this breaks whatever you have and you need to change every instance of the business object.  I'd love to hear a good explanation of this by OpenText development.

Brian Mellert

Alas, yet another reason I'm glad I haven't upgraded to 9.1.3.# yet, though I'd like to get the features which work.

I hope they QA 9.2 and Mobile 2, due out this quarter as I understand, better before release.

Robert Vignerot

To be fair, I've been using 9.1.3 since it came out without much trouble.

 

As for this particilar item about parameters, I'm not sure it is going to be different in 9.2, because I was under the impression from support that this was not a defect, but was working as expected. 

 

Jerome_Pearce

Rob,

 

Yet you mention a few problems on another thread. That "Working As Designed' is an old fallback position that really does not cut it with me. I used to have quite robust discussions with Support on the subject :smileytongue:. If it breaks what was working before, and what we have wriitemn code to use, it is just wrong. If they tell me that it is working as desinged, then the design is wrong!

 

I still feel that 9.1.3 is a QA fail.

 

---

Robert Vignerot wrote:

To be fair, I've been using 9.1.3 since it came out without much trouble.

 

As for this particilar item about parameters, I'm not sure it is going to be different in 9.2, because I was under the impression from support that this was not a defect, but was working as expected. 

 

---

Robert Vignerot

This really belongs in a different thread, but I think what constitutes a QA fail is very subjective, and considering the amount change that was needed to go to .NET 4, I was pleasantly suprised it was as stable as it was.  For what it is worth, my customer is moving to PROD on 9.1.3.0 after not beling able to get through UAT on 9.1.2.0, 9.1.2.1, and 9.1.2.2.

 

BTW - After speaking with OpenText, it sounds like the issue with parameters being used multiple times has been fixed/changed back in 9.2.