I would like to create a subscription with a delivery type "Write to BigQuery" and Use Topic schema and Write metadata options.
So i created Topic with following protobuf schema :
and a BigQuery table with additional columns for metadata specified in the docs.
When i try to create subscription with both Use Write Metadata and Use Topic schema options enabled, i get the following error:
API returned error: "Invalid schema definition: Could not parse schema."
Using just Write Metadata or just Use Topic schema works fine and i am able to create subscription and receive msgs
This appears to be an internal issue with how some nested records are processed. Please follow https://issuetracker.google.com/issues/267444753 for the investigation and fix.
Related
I am using confluent cloud to sink some data from Kafka to Salesforce via SObject Sink connector. The connection is made but I am running into an error "The Kafka record is missing the key _ObjectType which is used to identify the SObject. Please include the _ObjectType field in the record". Anyone has an idea of what is going wrong error?
Google searches aren't that useful as they lead me to Kafka Key/Value concept which is primarily for maintaining order of the messages
Are you trying to sink random records that you've created externally to the other connectors?
From overview docs
The Salesforce SObjects sink connector requires the Kafka records to have the same structure and format as the records output by the PushTopic source connector
So, if you aren't also using the "PushTopic source connector" or have records that deviate from the "structure and format" of those events (SObjects), then you should expect to see some error.
If I understand it right. You have to pass in the "Id" attribute along with its value in order to successfully write to salesforce. Because Id is the column which its value helps to identify if published record already exist or to be treated as an insert. Please try to pass in Id along with it value for example here in below I passed JSON payload as I have JSON converter in my configuration file for the connector.
"payload": {
"Id": "124421",
"FirstName": "name",
}
I created a data source on Azure Search via rest API. I use the API instead of portal, as I have a rowversion data type that isnt handled yet on portal. I am able to view the data source on portal
When I try to import the data source into an index, I get the following error
"Error detecting index schema from data source: "Data source payload should specify at least one of datasouce name and type"
What am I missing here?
I am using Salesforce connector to insert the customer details in the salesforce. I have used salesforce basic authentication configuration and operation used is "Create Single" and object type is "Account", and I am passing the whole payload to the salesforce connector. But when it hits the salesforce connector it throws error saying "Failed to invoke createSingle".
Can someone explain me why I am getting this error? Is there something that I am missing? I am unable to understand.
It was a miss from my side. The payload which I was sending to the connector had one extra field mapping and that is why it was throwing the error as the fields were not matching with the connector fields.
In OSB Layer when the endpoint uri is changed, I need to alert the core group that the endpoint has changed and to review it. I tried SLA Alert rules but it does not have options for it. My question is, the endpoint uri should be saved somewhere in the underlying database. If so what is the schema and the table name to query it.
URI or in fact any other part of OSB artifact is not stored in relational database but rather kept in memory in it's original XML structure. It can be only accessed thru dedicated session management API. Interfaces you will need to use are part o com.bea.wli.sb.management.configuration and com.bea.wli.sb.management.query packages. Unfortunately it is not as straightforward as it sounds, in short, to extract URI information you will need to:
Create session instance(SessionManagementMBean)
Obtain ALSBConfigurationMBean instance that operates on SessionManagementMBean
Create Query object instance(BusinessServiceQuery) an run it on ALSBConfigurationMBean to get ref object to osb artifact of your interest
Invoke getServiceDefinition on your ref object to get XML service
definition
Extract URI from XML service definition with XPath
Downside of this approach is that you are basically pooling configuration each time you want to check if anything has changed.
More information including JAVA/WLST examples can be found in Oracle Fusion Middleware Java API Reference for Oracle Service Bus
There is also a good blog post describing OSB customization with WLST ALSB/OSB customization using WLST
The information about services and all its properties can be obtained via Java API. The API documentation contains sample code, so you can get it up and running quite quickly, see the Querying resources paragraph when following the given link.
We use the API to read the service (both proxy and business) configuration and for simple management.
As long as you only read the properties you do not need to handle management sessions. Once you change the values, you need to start a session and activate it once you are done -- a very similar approach to Service bus console.
I am executing the query for my custom object created in SFDC. but i am getting the following error:
{'[{"message":"\nSELECT FS_Account_Name__c from FS_Work_Order__c\ERROR at Row:1:Column:34\nsObject type 'FS_Work_Order__c' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.","errorCode":"INVALID_TYPE"}]'} Thoough have written the correct table name as given while i created the Custom object. PLease help.
First thing to try: does it work properly when run as the system administrator profile? If so then it's certainly a permissions issue. Things to checl
The object is deployed (Setup > Create > Objects > Edit > Deployment Status)
The profile has permission to query the object.
If not, does that same query work from inside the developer console? If so I can't think of what it might be, except connecting to production instead of a sandbox or vice versa.