# UpdateActivationLogInfo
### Description
Updates the data associated with a license key.
The ActivationLog table is used when multiple licenses are issued from a single ActivationKey. In this case, the data associated with each activated computer is stored in the ActivationLog table instead of the LicenseKeys table. Therefore, to update data in the ActivationLog table, you need to specify which computer to update. The computerID, computerKey and computerName arguments can be specified to identify the computer. At least one of these arguments must be specified.
The ActivationLog table contains the following updatable fields: ComputerKey, ComputerName, ComputerID, ActivationDate, LastAccessedDate, ActivationCount
Note that to call this function, you must:
* Set the AdminEncryptionKey
```csharp
bool UpdateActivationLogInfo (string webServiceUrl, string activationKey,
string computerID, string computerKey,
string computerName, string licenseData,
out string response)
```
### Parameters
| Parameter | Type | Description |
| ------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| webServiceUrl | string | URL to the QLM License Server. |
| activationKey | string | activation key to update |
| computerID | string | the ID the computer to update |
| computerKey | string | the computer key to update |
| computerName | string | the computer name to update |
| licenseData | string | XML fragment containing the fields to update. The XML fragment should be of the form:
\field1=" 'value'
field2=" 'value' "
\
where field1 is the name of a field in the LicenseKeys table. For fields of type date, you should use the following date/time format: yyyy-MM-dd HH:mm:ss
Example:
\ComputerName= " 'my pc' "
UserData1=" 'my user data' "
\
|
| response | string | XML fragment containing the result of the call |
### Return
| Type | Description |
| ---- | --------------------------------------------------------- |
| bool | returns true if the operation succeeded; false otherwise. |
### Response XML format
```xml
Successfully updated license information for ActivationKey=XYZ.
```
### Example error response
```xml
Details about the error
```
**Important**: The value part of the licenseData xml fragment must be properly escaped for xml reserved keywords.
## Remarks
Use [ParseResults ](/docs/api-reference/.net-api/iqlmcustomerinfo/methods/parseresults.md)to interpret the results of the call and load the returned data into an [ILicenseInfo ](/docs/api-reference/.net-api/ilicenseinfo.md)object.
```csharp
ILicenseInfo li = new LicenseInfo();
string message = string.Empty;
if (lv.QlmLicenseObject.ParseResults(response, ref li, ref message))
{
// The operation was successful
}
else
{
// The operation failed
}
```
#### Example
```csharp
string userData = "Test&Go";
userData = SecurityElement.Escape(userData);
string licenseData = String.Format (@"\ ",
userData);
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.soraco.co/docs/api-reference/.net-api/qlmlicense/management-methods/updateactivationloginfo.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.