Yunique.Toolkit.API

<back to all web services

AppSettingUpdate

The following routes are available for this service:
PUT/v1/AppSetting/{SettingID}

To override the Content-type in your clients HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /xml/reply/AppSettingUpdate HTTP/1.1 
Host: plm.gerber.fila.com 
Content-Type: application/xml
Content-Length: length

<AppSettingUpdate xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs">
  <AppSettingData xmlns:d2p1="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs.POCOs">
    <d2p1:AppSettingComment>String</d2p1:AppSettingComment>
    <d2p1:AppSettingDescription>String</d2p1:AppSettingDescription>
    <d2p1:AppSettingGroupID>String</d2p1:AppSettingGroupID>
    <d2p1:AppSettingID>00000000-0000-0000-0000-000000000000</d2p1:AppSettingID>
    <d2p1:AppSettingKey>String</d2p1:AppSettingKey>
    <d2p1:AppSettingNote>String</d2p1:AppSettingNote>
    <d2p1:AppSettingOrder>0</d2p1:AppSettingOrder>
    <d2p1:AppSettingValue>String</d2p1:AppSettingValue>
    <d2p1:CDate>0001-01-01T00:00:00</d2p1:CDate>
    <d2p1:CUser>String</d2p1:CUser>
    <d2p1:ConfigFileName>String</d2p1:ConfigFileName>
    <d2p1:MDate>0001-01-01T00:00:00</d2p1:MDate>
    <d2p1:MUser>String</d2p1:MUser>
  </AppSettingData>
  <SettingID>String</SettingID>
</AppSettingUpdate>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<AppSettingUpdateResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs">
  <AffectedRows>0</AffectedRows>
  <status>String</status>
</AppSettingUpdateResponse>