• You are here:  
  • Home
  • Q&A
  • Q&A
  • SnapDevelop
  • Datawindow Converter Error with SnapDevelop 2019 R2

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (8)

Resolved Datawindow Converter Error with SnapDevelop 2019 R2

  1. Issue
0
Votes
Undo
  1. Thomas Rolseth
    Thomas Rolseth
  2. SnapDevelop
  3. Monday, 20 April 2020 13:39 PM UTC

I am in the process of migrating a web api from SnapDevelop R1 to R2.  We have about 50 datawindows that were exported to the api using the C# Model Generator.  The exported srd's and classes for these were in a 'DataWindows' folder along with the companion config file.  Per the migration instructions, I removed these from the project.  I then tried to use the Datawindow Converter but it is not working.  We are getting the following error regardless of which datawindow I try to convert:

ORA-00904: "C"."IDENTITY_COLUMN": invalid identifier

Our dw's are a mix of external datawindows and those with SELECT statements.  It's odd to me that an external datawindow would get this error.  In addition, if I try to preview the model in the Datawindow Converter window I get the attached error.

Before attempting to convert any of the datawindows, I was able to setup a connection to the Oracle (v12) database we use.  I also swapped out all of the old versions of the PB and SnapDevelop nuget packages with their newer counterparts.  Unfortunately, I can't do a successful build in SnapDevelop because it can't find the namespace for the dw models that no longer exist.

Did I miss a configuration setting or a migration step?  Any suggestions on how to resolve this issue?

Thanks, Tom

 

Attachments (1)
dw_converter_error.JPG dw_converter_error.JPG
  1. Migration
  2. C# Model generator
  3. SnapDevelop
  4. Web API
Migrate to Web Api how to export datawindows to PD...
Stored Procedures
Accepted Answer
Logan Liu @Appeon
Logan Liu @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 21 April 2020 08:50 AM UTC
  2. SnapDevelop
  3. # Permalink

Hi Tom,

For the error  "ORA-00904: "C"."IDENTITY_COLUMN": invalid identifier".

Identity Column is a feature introduced in Oracle 12c. Refer to:

https://oracle-base.com/articles/12c/identity-columns-in-oracle-12cr1

So were you connecting to an unsupported version of Oracle?

DataWindow Converter supports Oracle 12c or 18c, refer to:

https://docs.appeon.com/appeon_online_help/dwconverter2019r2/Working_with_DataWindow_Converter/index.html#selecting-the-database-connection

BTW: When converting models for external source DataWindows, it doesn't need to connect to the database. You can report a .NET DataStore bug to track it in the Appeon Standard Support at https://www.appeon.com/standardsupport/. 

Regards, Logan

Comment
Thomas Rolseth
  1. Thomas Rolseth
  2. Wednesday, 22 April 2020 15:30 PM UTC
Logan, as it turns out the database version is Oracle 11g which the Datawindow Converter does not support. I have reported a bug regarding the external dw issue.
  1. Helpful
Logan Liu @Appeon
  1. Logan Liu @Appeon
  2. Wednesday, 22 April 2020 17:20 PM UTC
OK. Thank you for your good question!
  1. Helpful
There are no comments made yet.
Responses (8)
Ricardo Jasso
Ricardo Jasso Accepted Answer Pending Moderation
  1. Wednesday, 22 April 2020 17:05 PM UTC
  2. SnapDevelop
  3. # 1

Solution Explorer Model Folder.

Attachments (1)
Solution Explorer - Models Folder.PNG Solution Explorer - Models Folder.PNG
Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Wednesday, 22 April 2020 15:09 PM UTC
  2. SnapDevelop
  3. # 2

screen shots of dw export process

Attachments (1)
dw_convert.pdf
Comment
There are no comments made yet.
Ricardo Jasso
Ricardo Jasso Accepted Answer Pending Moderation
  1. Wednesday, 22 April 2020 14:52 PM UTC
  2. SnapDevelop
  3. # 3

Models folder.

Attachments (1)
Model Export.PNG Model Export.PNG
Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Tuesday, 21 April 2020 13:54 PM UTC
  2. SnapDevelop
  3. # 4

Also, we were using the same database with SnapDevelop R1 and the C# Model Generator worked fine.  Since the database is the same, it feels to me like something has changed in SnapDevelop R2 with respect to how it works with an Oracle 12 database.

Comment
Logan Liu @Appeon
  1. Logan Liu @Appeon
  2. Wednesday, 22 April 2020 02:28 AM UTC
Yes. The whole implementation of .NET DataStore is different from 2019 GA. Now with 2019 R2, .NET DataStore has removed the dependency on the original DataWindow SRD file. Refer to:

https://docs.appeon.com/appeon_online_help/snapdevelop2019r2/Features_List/index.html#refactored-net-datastore
  1. Helpful
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Tuesday, 21 April 2020 13:50 PM UTC
  2. SnapDevelop
  3. # 5

"BTW: When converting models for external source DataWindows, it doesn't need to connect to the database. "

That may be true but I am always prompted to make a database connection when I try to export a datawindow using the Datawindow Converter.  Is there a way to suppress that for an external dw?

Comment
Logan Liu @Appeon
  1. Logan Liu @Appeon
  2. Wednesday, 22 April 2020 02:23 AM UTC
There is no way to suppress that for an External Source DataWindow now. You can report a .NET DataStore bug to track it in the Appeon Standard Support at https://www.appeon.com/standardsupport/.
  1. Helpful
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Monday, 20 April 2020 18:36 PM UTC
  2. SnapDevelop
  3. # 6

Models screenshot

Attachments (1)
models.JPG models.JPG
Comment
There are no comments made yet.
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Monday, 20 April 2020 18:03 PM UTC
  2. SnapDevelop
  3. # 7

I also created a test API and tried to convert a single 5-column external datawindow using the new tool (no sql).  I got the same error as posted above when using Oracle.  However, when I tried it with SQL Anywhere the process ran fine and a Models folder was created in the project (along with the corresponding model class for the dw).

Comment
Load more comments
Thomas Rolseth
  1. Thomas Rolseth
  2. Wednesday, 22 April 2020 15:07 PM UTC
I tried this again and it did not do what I would expect. Please look at the word document attached -- I took screenshots of each step in the process. The export of the external dw worked and it created the Models folder along with the newly exported class. However, it did not add the new Models folder to the solution in SnapDevelop. I have to manually add it in the Solution Explorer. That was handled automatically in SnapDevelop R1.
  1. Helpful
Ricardo Jasso
  1. Ricardo Jasso
  2. Wednesday, 22 April 2020 17:05 PM UTC
It works for me (see attachement). Tested it againg deleting the folder. Maybe you should try recreating the whole test again to verify.
  1. Helpful
Thomas Rolseth
  1. Thomas Rolseth
  2. Wednesday, 22 April 2020 22:17 PM UTC
I did as you suggested and created a new API solution. This time it worked. Something must have gotten out of sync. Thanks.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.