Can you provide the full exception / stack trace so we can see where the exception is being thrown?
Hi Robert, here is the Exception.
We will be happy to have a screen share session were you can check the code and suggest some work around.
I think we have a reference issue when we are updating the DuctBankConfig object.
System.NullReferenceException was caught
Message=Object reference not set to an instance of an object.
at Miner.Interop.MMDuctBankConfigClass.SaveToField(IRow pRow, Int32 lColumnIndex)
at TestCommand2.DuctManagement.OnClick() in C:\Users\Prasad\Documents\Visual Studio 2010\Projects\TestCommand2\TestCommand2\DuctManagement.cs:line 257
If you edit the feature manually, do you still get this exception? If so, it's likely to be either a data or configuration problem. You already know this, but I'd double check all your field model names and try experimenting around with trying to get it working using the OOTB tools then reproducing it with your custom tool. What is this tool doing?
Robert, I think we figured it out. We were testing the tool with only the single conduit feature class added to the ArcMap.
Once, we added the entire Conduit dataset and the UFM dataset the tool worked without any exception.
I guess the exception was due to Autoupdaters not firing.
It actually sounds like one of the autoupdaters requires you to have a certain map layer present in order to function. I know that some of the AUs (like the ones that update conduit cross sections) require that you have certain layers present in your map, although in the past they've usually been pretty good about logging errors instead of causing edits to fail. Glad you got it figured out!