[Ethereum] Unable to add new struct item into mapping or array

Summary

The issues are:

1. The default gas for a transaction executing a contract is 90,000 . Your statement to execute addItem() does not specify the gas amount so 90,000 is assumed. The execution of this addItem() method took 226,554 gas.
2. The getItem(...) method should be marked constant to return the values correctly.
3. The countItemList() method should also be marked constant to return the value correctly.
4. And as @Tjaden Hess commented below, your statement listarratcontract.AddItem.call({data:{name:"item2",iid:2,code:"i2",val:2}}) does not execute the method as a transaction modifying the blockchain data. See below for the statement to execute this method as a transaction. See What is the difference between a transaction and a call? for further information.

Details

I've made some minor changes to your source code:

• Formatting.
• Marking countItemList() and getItem(...) as constant.
• Commenting out log0(itemnew) as this statement causes an error in my Browser Solidity / geth.

Here is the source code:

pragma solidity ^0.4.0;

contract ItemListContract {
    struct item {
        bytes iname;
        uint16 itemid;
        bytes icode;
        uint ivalue;
    }

    uint itemCount;
    mapping(bytes => item) itemList;
    item[] itemArray;

    function ItemListContract() {
        log0('hi');
    }

    function addItem(bytes name, uint16 iid, bytes code, uint val) {        
        var itemnew = item(name, iid ,code, val);
        // log0(itemnew);
        itemList[code] = itemnew;
        itemArray.push(itemnew);
        itemCount++;
    }

    function countItemList() constant returns (uint count) {     
        return itemCount;
    }

    function removeItem(bytes code) {
        delete itemList[code];
        itemCount--;
    }

    function getItem(bytes code) constant returns (bytes iname, uint val) {   
        return (itemList[code].iname, itemList[code].ivalue);
    }
}

The following screenshot of your code being deployed and executed using Browser Solidity shows that the addItem(...) method took 226,554 gas.

Calling getItem(...) returned the value added in the call to addItem(...). And calling countItemList() returned 1.

The following section shows the execution of your contract methods using the geth command line and the increased gas amount:

> var itemListABI = [{"constant":false,"inputs":[{"name":"code","type":"bytes"}],"name":"removeItem","outputs":[],"payable":false,"type":"function"},{"constant":true,"inputs":[],"name":"countItemList","outputs":[{"name":"count","type":"uint256"}],"payable":false,"type":"function"},{"constant":true,"inputs":[{"name":"code","type":"bytes"}],"name":"getItem","outputs":[{"name":"iname","type":"bytes"},{"name":"val","type":"uint256"}],"payable":false,"type":"function"},{"constant":false,"inputs":[{"name":"name","type":"bytes"},{"name":"iid","type":"uint16"},{"name":"code","type":"bytes"},{"name":"val","type":"uint256"}],"name":"addItem","outputs":[],"payable":false,"type":"function"},{"inputs":[],"type":"constructor"}];
undefined
> var itemList = eth.contract(itemListABI).at("0xee7b790b638553cc95a4355d422536bad1566fd7");
undefined
> itemList.addItem("item3", 3, "i3", 3, {from: eth.accounts[0], gas: 500000});
"0xc70469c662c759627c217827845a6567ff1ac1dd2ebd5e0d52fe817aeeb7867a"
> itemList.countItemList()
3
> itemList.getItem("i3")
["0x6974656d33", 3]

Gas Cost Differences - Responding To Question In Comments

addItem(...) Gas Cost Differences

I called addItem(...) 4 times with the following parameters and the associated gas cost:

• "item1", 1, "i1", 1 - 226,554
• "item2", 2, "i2", 2 - 196,554
• "item3", 3, "i3", 3 - 196,554
• "item4", 4, "i4", 4 - 196,554

Following is the Browser Solidity screenshot:

I ran a debug.traceTransaction(...) for the first and second operation to find the differences in the gas cost.

Here is a screenshot showing the first difference in gas cost:

And here is a screenshot showing the second difference in gas cost:

Here is the code for addItem(...):

function addItem(bytes name, uint16 iid, bytes code, uint val) {        
    var itemnew = item(name, iid ,code, val);
    // log0(itemnew);
    itemList[code] = itemnew;
    itemArray.push(itemnew);
    itemCount++;
}

The difference in gas cost between the first and second operation is (20,000 x 2) - (5,000 x 2) = 30,000 for the SSTORE operation when assigning itemnew to itemList[code] and itemArray.push(...).

From the fee schedule in the Ethereum Yellow Paper, you can see that the first SSTORE operation to store the new data in itemList and itemArray sets the storage value from zero to non-zero and costs 20,000 gas (highlighted in green below).

The second SSTORE operation to store the new data in itemList and itemArray sets the storage value from non-zero to non-zero and costs 5,000 gas (highlighted in pink below).

removeItem(...) Gas Cost Differences

I then called removeItem(...) 4 times with the following parameters and the associated gas cost:

• "item1" - 48,181
• "item2" - 48,181
• "item3" - 48,181
• "item4" - 33,181

Following is the Browser Solidity screenshot:

You can run a debug.traceTransaction(...) for the third and fourth operations to find the differences in the gas cost.