Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
Hi Clive,
By the error message, it looks as though you are using the SboEwsRestProvider, but its name, of course it will work with SBO, but it does have a lot of specifics that need to be done for it to work fully, beyond a simple configuration. We don't generally suggest using the Sbo provider except in certain circumstances.
That said, I would suggest for you to use the SoapEwsRestProvider instead, in your situation, I think likely the error will go away.
As far as the specific error, the SboEwsRestProvider, is a hybrid implementation that uses some CSP (EBO's native protocol) and EWS behind the scenes. Because of the way CSP works, we need to manaully let Smart Connector know which COML (EBO's object model) types are valid for a specific EWS type (e.g. containers, values, trends, alarms). It is likely that this BACnet trend type, isn't in this mapping. This mapping table is actually in the Smart Connector database in the ComEwsMappings table. So basically, to fix it, you would need to figure out the fully qualified COML type of the trend log in question, and then add it to this database table manually, and then restart your REST endpoint.
In order to determine the fully qualified COML type name, you can log into EBO, view the properies of the object in question (in this case the Trend log), expand the 'General Information' tab, and the hover over the Type name: See below for screenshot example (the COML type for the example below is trend.TLog😞
The above is kind of a convoluted, this is why we suggest using the SoapEwsRestProvider, as it is more than capable in the vast vast majority of use cases, and it just works :).
Let me know if you have anymore questions.
Best Regards,
-Jeff
Link copied. Please paste this link to share this article on your social media post.
Hi Clive,
By the error message, it looks as though you are using the SboEwsRestProvider, but its name, of course it will work with SBO, but it does have a lot of specifics that need to be done for it to work fully, beyond a simple configuration. We don't generally suggest using the Sbo provider except in certain circumstances.
That said, I would suggest for you to use the SoapEwsRestProvider instead, in your situation, I think likely the error will go away.
As far as the specific error, the SboEwsRestProvider, is a hybrid implementation that uses some CSP (EBO's native protocol) and EWS behind the scenes. Because of the way CSP works, we need to manaully let Smart Connector know which COML (EBO's object model) types are valid for a specific EWS type (e.g. containers, values, trends, alarms). It is likely that this BACnet trend type, isn't in this mapping. This mapping table is actually in the Smart Connector database in the ComEwsMappings table. So basically, to fix it, you would need to figure out the fully qualified COML type of the trend log in question, and then add it to this database table manually, and then restart your REST endpoint.
In order to determine the fully qualified COML type name, you can log into EBO, view the properies of the object in question (in this case the Trend log), expand the 'General Information' tab, and the hover over the Type name: See below for screenshot example (the COML type for the example below is trend.TLog😞
The above is kind of a convoluted, this is why we suggest using the SoapEwsRestProvider, as it is more than capable in the vast vast majority of use cases, and it just works :).
Let me know if you have anymore questions.
Best Regards,
-Jeff
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.