// create new Thing var params = { name: ThingName /* STRING */, description: undefined /* STRING */, thingTemplateName: "Timer" /* THINGTEMPLATENAME */, tags: undefined /* TAGS */ }; Resources["EntityServices"].CreateThing(params); // read initial configuration // result: INFOTABLE var configtable = Things[ThingName].GetConfigurationTable({tableName: "Settings"}); // update configuration with service parameters configtable.updateRate = updateRate configtable.runAsUser = user // set new configuration table var params = { configurationTable: configtable /* INFOTABLE */, persistent: true /* BOOLEAN */, tableName: "Settings" /* STRING */ }; Things[ThingName].SetConfigurationTable(params);
I have currently a taks where this code is helpful but my quesiton here.
Do we need to set the thingname in the param json? like:
// create new Thing var params = { name: ThingName /* STRING */, description: undefined /* STRING */, thingTemplateName: "Timer" /* THINGTEMPLATENAME */, tags: undefined /* TAGS */ };
params.name=ThingName; Resources["EntityServices"].CreateThing(params); ....
or is already done in the param definition? Means the input parameter is used . No problem I will test it
Hi Roland,
the "ThingName" is a service parameter and reused to substitute the name aspect of the params JSON.
You can either set it explicitly or use variables. As long as the parameter is passed correctly to the CreateThing service, it doesn't matter if it's set directly in the params or added later on - but it has to be part of the parameters once the CreateThing service is called.
I have used the ThingName as service parameter and not hardcoded, as I can create dynamic named Things with it - and the name will be used multiple times during the service call, e.g. to call the GetConfigurationTable service.