OData Service Catalog Discovery fails if extensions are set incorrectDescriptionIssue Description: The issue arises when the MID server user lacks sufficient access to the "sn_erp_integration_odata_catalog_service" table, which is necessary for attaching the XML to the table record. This problem can be observed in the Flow Designer during the action "Parse OData Service", where an error message similar to the following may appear: "Failed to fetch EDMX file: TypeError: Cannot convert null to an object. (Process Automation.db4779caffe85210ecdbffffffffff02; line 6)." This error indicates that the necessary access rights to perform the operation on the sn_erp_integration_odata_catalog_service table are not granted to the MID server user. Resolution: To resolve this issue, you must apply the update set to ensure the MID server user has the correct access rights and configurations for interacting with the sn_erp_integration_odata_catalog_service table. Follow these steps: Download the Update Set: Locate and download the following update set: sys_remote_update_set_4d214f9e47355610d6f6e889116d43a8.xml.Apply the Update Set: Navigate to the Update Sets module in ServiceNow.Import and commit the downloaded update set to your instance.Verify Access Permissions: After applying the update set, ensure that the MID server user now has the appropriate permissions to access the sn_erp_integration_odata_catalog_service table.You can verify this by checking the access control rules associated with the table.Test the OData Discovery: Once the update set is applied and permissions are confirmed, re-run the OData Service Catalog Discovery process to verify that the issue is resolved.By following these steps, you should be able to resolve the error and allow the OData Service Catalog Discovery to complete successfully without further issues.Steps to Reproduce Found at PoC Customer Glencore1) Create a new system (without the extension set)2) System will automatically start a flow "Get SAP BAPIs and tables when system becomes active" to download all the required information about the system like "Tables", "RFC" and OData catalogue.3) This flow internally calls "Get OData Catalog Service Data" which will start the action "Read Catalog Service" will start and fail - status for retrieval will remain in status 'In progress'WorkaroundApply the update set: sys_remote_update_set_4d214f9e47355610d6f6e889116d43a8.xmlRelated Problem: PRB1824431