Overall bug on Innovator

In my opinion, the problem comes from the method : cui_reinit_calc_tearoff_states

Hello,

Could you try to open up the method cui_reinit_calc_tearoff_states and save it? You shouldn't need to make any changes to the Method itself, just click the Edit button in the form and then immediately click Done.

Chris

Christopher Gillis

Aras Labs Software Engineer

The cui_reinit_calc_tearoff_states doesn't exist. Can you send it to me ?

The only method that exists, with almost the same name, is the following :

And the toolbar is weird :

Thank you. best regards

Our testing of Aras Innovator is stopped. Can you send us the cui_reinit_calc_tearoff_states method or give us a solution to our issue ?

Thank you

Hi AlBer,

I've made a gist with the code for this method that you can find here.

https://gist.github.com/cgillis-aras/e0ce6b00b3408a79c51a17e228a3db24

You can try manually creating the method, but it should exist in the database by default. I'm not sure of how it got removed. Since you said you only started seeing this issue this week, do you have a backup of the database from before last weekend that you could restore to?

Chris

Hello,

Thank you for your answer.

Sadly, I don't have any backup of the database.

Is there a way to simplify the package creation without selecting all ItemTypes, Relationships, Forms, Permissions, ... ?

Hello,

Thank you for your answer.

Sadly, I don't have any backup of the database.

Is there a way to simplify the package creation without selecting all ItemTypes, Relationships, Forms, Permissions, ... ?

You may be able to find a clean InnovatorSolutions database in your install folder under /DB/CoreAndSolutions120.bak. This backup will not contain any of your data or customizations, but it will contain all of the default ItemTypes, Methods, etc. as if you had just installed Aras Innovator. You might be able to restore that backup with a new name, export all of the standard packages from that database, and try to import them into your existing database to reset all of the standard items. 

If you continue to see issues, you can try doing the opposite to restore that backup with a new name and then move all of your customizations and data from your existing database into that clean database. Doing this, there will not be an simpler way of packaging your customizations than selecting each item you have added and running the action to add it to a package.

Okay,

Thank you very much for your answer !

Best regards