CODEWITHSUNDEEP
node.jsazureazure-storageazure-table-storage
p.campbell
p.campbell

Reputation: 100637

Adding PartitionKey propery when inserting an entity in Azure table storage for nodejs

This is more of a call for help with an exception when calling insertEntity().

I'm using Nodejs on Azure and editing in Monaco, and I've NPM-installed the latest version of azure storage.

The exception I encounter is: (full stack trace at the bottom)

Unaught exception: Error: Parameter entityDescriptor.PartitionKey for function entityOperation should be an object at ArgumentValidator._.extend.object

I'm basically taking my object to save, and creating 2 new properties: PartitionKey and RowKey. I give them string values. I'm following the examples. I'm not using entityGenerator, as the samples here don't, whereas the examples on the Azure Node developers portal do. I wouldn't mind using entityGenerator on the storage-specific properties if required, but the samples in the node azure github repo seem to suggest that you can use simple strings. The entityGenerator looks a bit ugly and cumbersome, honestly, as you'd have to code extra around the entity when you bring it back.

How can I adjust my code to solve this problem and call insertEntity() with success?

exports.saveTally = function(tally, callback) {
    var tableSvc = getAzureTableService();
     tableSvc.createTableIfNotExists("tally", function(error, result, response) {
if (!error) {    
  tally.PartitionKey="tally";
  tally.RowKey = tally.id;       
  tableSvc.insertEntity("tally", tally, function(error, result, response) {
    if (error) {
      console.log("*Error saving tally " + error.toString());
    }
    else {
      callback(tally.id);
    }
  });
}
});}

stacktrace

Upvotes: 1

Views: 2094

Answers (1)

Emily Gerner
Emily Gerner

Reputation: 2457

The location of the Azure storage client library has changed to https://github.com/Azure/azure-storage-node. The samples you’re using are from the old location and from an older version of the library which is why they’re not working. You’ll find updated samples and code at the new location.

In the newer version, an Edm type must be specified for each table entity. This is because type is stored in the storage service and we want to make sure that we are storing what you intend. Each table entity is an object with the form {_:value, $:Edm.Type}.

Entity generator is a convenience feature which makes it simpler to construct table entity objects. We return entities in the form just mentioned and using this convenience feature will not change that in any way.

Upvotes: 1

Related Questions