Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
Two minor notes:
- When creating a CorrectBusinessTransactionRequest you also need to attach CorrectionBusinessTransactionFields.
It doesn't have any properties and thus not holding any data, but is still needed in the request. - The CorrectionBusinessTransaction is not a special transaction type, but simply a wrapper that incapsulates SuperTransaction Ids.
| Name | Type | Description | Mandatory | Available from version |
|---|
| BrickId | Guid | Ids of SuperTransactions to be corrected | Yes | 2,14 |
Outputs
| Name | Type | Description | Available from version |
|---|
| Entities | Array | Entites containing the BrickId (unique id) of the SuperTransactions |
|
Code examples
public static void CorrectBusinessTransaction()
{
var binding = new BasicHttpBinding();
binding.MaxReceivedMessageSize = Int32.MaxValue;
var target = new bfsapi.bfsapiSoapClient(binding, new EndpointAddress("http://localhost:20010/bfsapi.asmx"));
var req = new bfsapi.CorrectBusinessTransactionRequest();
req.Credentials = new bfsapi.Credentials
{
UserName = "username",
Password = "password"
};
req.identify = "identity";
req.Fields = new CorrectionBusinessTransactionFields();
req.Entities=new CorrectionBusinessTransaction[]
{
new CorrectionBusinessTransaction
{
BrickId = new Guid("e14ee5c1-cc78-4dad-bf0a-14800538a107")
},
};
var resp= target.CorrectBusinessTransactions(req);
}
