Failed to execute deployed method 'DataValue', using entity. DataType property mismatch

Hi,

I've encountered a rather frustrating error using one particular editable grid, and wondered if anyone else has had this?

The scenario is this.

I have a bunch of editable grids using pretty much every Metastorm type (text, real, datetime etc), used throughout various forms in a process. All of them are working fine EXCEPT for one.

The grid that is failing has a couple of text values and a single datetime column defined. The business object behind the grid is defined directly on the table to be edited and "seems" to have correctly identified the types for the table columns.

When I add a new row or delete a row I get the following error: (I've changed the grid name to "Grid1" and DateTime column to "StartDate" just for the example)

Failed to execute deployed method 'DataValue', using entity 'Grid1'. .StartDate and .StartDate have conflicting properties: DataType property mismatch.

1) I've tried deleting the grid and the business object, and then re-creating them, but that doesn't seem to work.

2) I've also gone through the MBO XML file to check the data type defined in the Business Object for the target column and that is defined as a "DateTimeType" too.

3) I've changed the column type to "Text" for the DateTime column, but that makes the column Read-Only because the underlying column is of DateTime. This at least allowed the grid to be edited (inserts and deletes), but is no good as a solution.

I'm probably going to have to create a workaround for this one grid due to time constraints by creating a bunch of fields next to a read-only grid and having some command buttons to insert into the grid, but I'd really like to figure out what is going wrong here.

Any pointers appreciated. (Version 9.1.2..3 (SQL Server))

Thanks

Phil

Find more posts tagged with

BPM

Comments

Jerome_Pearce

The first thing I would check is the actual data type in the database. Did you create it using the designer? If not, is it the same data type as the Designer would create? Are you sure your data connection is pointing to the same database used by the deployment service (just one of the several problems that can be caused by using multiple deployment services from one Designer)?

McGaw_Phil

Hi Jerome,

The data type for the column that is reporting the error is of DateTime, which is what the Designer would create for a DateTime variable. I was tempted to change the column type in the database to just DATE, but decided against it.

The target table was created via a SQL Script outside of the Designer, along with other tables that are working fine as editabe grids with dates.

The underlying table is on a different database to the Metastorm one, so not sure if the deployment service would come into this scenario. The target database resides on the same server as the Metastorm one too, and the connectionstring for the connection is correct.

This problem feels like I have some sort of corruption in the XML, but I've gone through this and all appears fine, without digging down into the Guids and whatever the key with the "pref_123456" represents.

Thanks
Phil

Jerome_Pearce

Do other similar grids with datetime columns on this database work? If not, it is the connector to that database.

McGaw_Phil

Yep, all the other grids work fine.

I'll try re-creating the connection, but won't that blast all the Business Objects using that connection?

Brian Mellert

I have encountered this a couple of times .. and the tables were defined by MBPM itself, not externally. Though in my case the date column was a hidden column.

It worked for the longest time, then started generating this error even though the grid / BO columns hadn't changed.

To get around this issue for now (have a demo with the sponsor) I removed the column from the grid. I may try to restore it after the demo to try to figure out more. However, meanwhile I will be curious if others can chime in on this.

Jerome_Pearce

I was certain that this was not the issue from your initial description of the error, but are any parameters set that should be datetime but are set to text (the default)? It is one of the most common errors, and produces an error message similar to this I think.

Another Q: when do you get the error? From your description I assume it is on submitting the form.

McGaw_Phil

The error occurs on submit of the form if you try deleting or adding data to the grid.

All columns on the grid and parameters on the business object are set to the correct type.

I'm going to try re-creating the editable grid in a completely new solution, pointing it at the same table and see what happens.

For reference, the stack trace says it is failing on the method System.Data.Merger.MergeSchema(DataTable table), but on searching for this in google as a purely .NET related error, there isn't much there.

Will let you know how I get on.

Fadil Kadir

I had this one as well, I logged in as the metastorm service account and changed the regional settings accordingly and the date format was resolved.

McGaw_Phil

Re-created the editable grid in a completely new solution, pointing to the same underlying Sql table/Business Object, on the same database. Setup every column exactly the same, and now it works fine.

Answer...Inconclusive.

Jerome_Pearce

I just had a 'blast from the past' memory. If you create an editable grid by dragging & dropping from the BO pane, it can fail. If you create it 'manually' it will work. I forgot about this because we never create editable grids like this ever since we discovered the error. I do not think anyone else has reported it, and as there was a simple workaround I did not bother.

McGaw_Phil

Hi Jerome,

When you say "create it manually", what exactly do you mean?

To achieve an editable grid, the steps I would normally follow would be to:

Create the new business object from the "Repository" tab
Go to the form I want to have an editable grid on and drag the newly created business object from the "Toolbox" tab on to the form
Create my grid on the form and then associate the business object with the grid.

Is there another way?

Thanks

Phil

Brian Mellert

I believe Jerome is referring to creating a grid from the toolbox instead of creating it from drag/drop of the BO itself. You'd then assign the BO in the grid properties and columns from there.

I've not had an issue either way -- yet anyway -- but our big v7 processes will hopefully start being converted to v9 soon in which it may become more of an issue.

Jerome_Pearce

Yes, that is what I meant.