Log in to AnswerLog in to Follow
UserImage.jpg
Shailendra Shrivastava
30Views
2Comments
[BulkInsert] BulkInsert issue in application post platform upgrade
Question
Forge
OutSystems 11
Service
bulkinsert
Service icon
BulkInsert
Forge component by Galter
Application Type
Service
Service Studio Version
11.14.16 (Build 60354)
Platform Version
11.18.1 (Build 37905)

Hello Team,

We have upgraded our platform from 11.12.1 to 11.18.1. Post upgrade we are facing an issue in the application for the screenshot has been attached.

After seeing this issue, we have upgraded the BulkUpload Extension from the Forge. After upgradation and refresh the modules that consume this extension we are getting some strange problem . 

Now when we are refreshing the dependencies of bulkinsert and publish the app from Service Studio, there are no errors. Application works fine.

But, when we refreshed / published the app via Service Center via solution, we get the below errors. 

This seems pretty weird and are stuck with upgrade since we cant proceed without fixing it.

Thanks,

0
0
06 Feb

Hello!

There was a change in platform version 11.18.0 that affected this extension: "Improved the DLL loading mechanism of Platform Services and Applicational Runtime for Database Connectors/Plugins and their referenced DLLs. This may bring breaking changes to some third-party/custom Database Connectors/Plugins (built with the Database Connector SDK) and some assets available on Forge. Find more about these breaking changes here. (R11BRT-173)".

This extension relied on the platform's database drivers, which now are only available when an external database connection for the database exists. Including the drivers in this extension can lead to conflicts with the platform drivers, so it's not a straightforward fix.

If you read through the details of this breaking change there's a workaround that doesn't involve changing the extension: 

  1. Identify the assembly that's failing to be loaded in the list above.
  2. Create a new External Database Connection and chose the DBMS identified on the list.
  3. Don't test it and then save it. This will be a dummy connection, used only to recreate the files. It doesn't need to be assigned to an extension.
  4. Republish the app that was having the errors.

I hope this helps.




0
0
06 Feb

Thanks for you response

As per your suggestion , we will definitely check the breaking changes. but the main issue is here that when we are refreshing the dependencies and publish the module without any changes from the Service Studio/OutSystems App, we don't get errors and application works fine. But when we publish the same module from the service center via solution so we started getting the error messages.  

0
0
06 Feb
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.