Author Topic: Compatiblity issue of Composer  (Read 1726 times)

Offline kevinwang

  • Full Member
  • ***
  • Posts: 151
  • Karma: 0
Compatiblity issue of Composer
« on: July 12, 2012, 11:25:40 PM »
I developed ivr callflow using composer 8.0.401.84,  exported project, imported into composer  8.1.101.88,  but when I tried to open callflow,

I got the following error message:

Cannot open input element:

Reason:
Value:

'com.genesyslab.studio.model.gvp.datatypes.impl.PromptItemImpl@10d16b(name:noinput1)(value: Language/1000.vox)(interpretAs: Text,type:Value,alternateText: , format:, note:, instruction:, ........'


Is there anyone who experienced similar problem?

Thanks in advance.

Kevin



Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1789
  • Karma: 57
Re: Compatiblity issue of Composer
« Reply #1 on: July 13, 2012, 05:29:23 AM »
Hi Kevin,

Have you upgraded your project created with Composer 8.0.401.84 before opening it with version 8.1.101.88?

R.

Offline kevinwang

  • Full Member
  • ***
  • Posts: 151
  • Karma: 0
Re: Compatiblity issue of Composer
« Reply #2 on: July 13, 2012, 10:05:06 PM »
Hi Kevin,

Have you upgraded your project created with Composer 8.0.401.84 before opening it with version 8.1.101.88?

R.

Thansk, Rene, good point. I didn't upgrade. but I just tried, there is still a error msg.

"The upgrade process has ran into an error. Please see Details and check the logs".

When I opened details:  there is java NullPointer error.

java.lang.NullPointerException.

Offline kevinwang

  • Full Member
  • ***
  • Posts: 151
  • Karma: 0
Re: Compatiblity issue of Composer
« Reply #3 on: July 13, 2012, 10:23:37 PM »
Hi Kevin,

Have you upgraded your project created with Composer 8.0.401.84 before opening it with version 8.1.101.88?

R.

Thansk, Rene, good point. I didn't upgrade. but I just tried, there is still a error msg.

"The upgrade process has ran into an error. Please see Details and check the logs".

When I opened details:  there is java NullPointer error.

java.lang.NullPointerException.

Thanks, It works now.