Monarch 10 user upgrade to 11...
I've used various versions of Monarch/Datawatch dating back to version 3 in 2005ish. Recently required to upgrade from 10 to 11 due to XML4 no longer being supported.
I'm finding it difficult to incorporate all my existing models (both in .mod & .xmod formats); any suggestions on how this new version works to use establish Models? Its not as intuitive as I thought.
Additionally now that I think I've figured some of it out I continue to get an error when using the Table -> Data View after applying the external model I get an error: "An unexpected error occurred while building the data view. Object reference not set to an instance of an object." The only option at this point is to click OK which also completely kills the application and I have to start from scratch.
Any information/suggestions would be greatly appreciated.
Answers
-
Mike,
Firstly which release of Monarch V11 do you have?.
11.5 was quite a significant change.
That said most models should still work unless perhaps you have some really old .mod files.
It's a while back now but I seem to recall that at some point direct conversion of certain very old .mod files was no longer available (on the basis that things had changed over the years and very few people were likely still on the old models or had not already upgraded them during previous version updates along the way.
Putting that aside, once into V11 things like MS Windows .NET versions come into play (and associated patches and updates).
The error is a generic Microsoft error message - it could perhaps be more helpful!
If you search for the message (as you probably have) you will likely get a very large number of hits.
I'm fairly sure it has been discussed here previously but whether a forum search will find a useful reference quickly that is in line with your specific problem I cannot be sure.
Tell us which release of V11 you now have and we can take it from there.
Grant
0 -
Altair Forum User said:
Mike,
Firstly which release of Monarch V11 do you have?.
11.5 was quite a significant change.
That said most models should still work unless perhaps you have some really old .mod files.
It's a while back now but I seem to recall that at some point direct conversion of certain very old .mod files was no longer available (on the basis that things had changed over the years and very few people were likely still on the old models or had not already upgraded them during previous version updates along the way.
Putting that aside, once into V11 things like MS Windows .NET versions come into play (and associated patches and updates).
The error is a generic Microsoft error message - it could perhaps be more helpful!
If you search for the message (as you probably have) you will likely get a very large number of hits.
I'm fairly sure it has been discussed here previously but whether a forum search will find a useful reference quickly that is in line with your specific problem I cannot be sure.
Tell us which release of V11 you now have and we can take it from there.
Grant
Hello Mike,
V11? Poor you. Up to 11.4 it was pretty buggy, 11.5 onwards killed automation. But it's all xmod still, unlike the dmod from v12 onwards, asnd it ships with Utility. You can also import and export objects between models - so if you have a bad model that won't open, try opening the report in a new session, and then pulling in the templates, fields, filters etc definition by definition into the new model.
Best wishes,
Olly
0
Altair Employee