M.App Enterprise Discussions

[khaled]

Dear all,

I am using MAE 16.5, and I built a workflow desktop application but whenever I try to open a workflow form or list, it gives me the following error message

The field 'geom' has type 'public.geometry', which is currently unknown to Npgsql. You can retrieve it as a string by marking it as unknown, please see the FAQ.‎

Note: I originally built the workflow on MAE 16.1.4 then migrated it into 16.5.

I am using database postgres 9.6 with postgis 2.5.0.

Best Regards

Khaled 

[sturcato]

hi Khaled,

can you please post here your table definition?

Stefano

[khaled]

Dear Stefano,

Kindly find attached file.

Regards

Khaled

[sturcato]

sorry, I meant the "create table" sql statement.

[khaled]

Hi Stefano,

[sturcato]

I cannot replicate your issue. I've loaded your table and your workflow (removing only references to additional tables) and I can successfully capture data and load lists and forms.

Is there anything else in your workflow definition that can cause problems?

[khaled]

Hi Stefano,

Now I get in the error log another error as follows:

‎c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\workflows\d4a0faa0\5c7ee588\App_Web_listheadertemplate.cshtml.5e279d63.zdb5velh.0.cs(65): error CS0103: The name 'nameof' does not exist in the current context‎

Although I did not change anything.

I also tried another sample shapefile from https://www.mapbox.com/help/data/stations.zip but the same error of the NPGSQL, I investigated the error and it appears that the npgsql.dll 4.0.3.0 which is used in MAE 16.5 does no longer support the types of POSTGIS itself, but there a specialized spatial library 'NetTopologySuite' should be used as stated in https://www.npgsql.org/doc/types/nts.html. I hope this note would help.

Best Regards

Khaled

[sturcato]

hi Khaled,

I'm not quite sure I've got your point. The way it is implemented keeps compatibility with the past, so you don't have to take care of any change. 

As I said we are not able to replicate this issue, we have tested several environments including a Postgres 9.6 server with PostGIS 2.5.

I guess there is something wrong on your server installation.

Stefano

[khaled · Accepted solution]

I reinstalled the M.App Enterprise 16.5.1 again and it worked now.

Thanks

Khaled