I am running geoevent extension 10.3.1. I have created an input and defined its geoevent definition. I have then created an intermediate geoevent definition with some extra fields and mapped that to the input definition. These extra fields will be populated with values from field calculators further down the data flow. Everything works fine until I decide that I need to add a new field to the intermediate geoevent definition in order to calculate this field later. The moment I edit the intermediate geoevent definition the data stops flowing through to the output. Even though I have only added an extra field, and I would have expected this to work but to add that field with null values until I calculate them myself.
If I delete the geoevent service and recreate it everything works ok. Does anyone know why this is happening and what I can do to prevent it?
The reason I am doing it this way is I do not want to have to handle all the managed definitions that get created when you add multiple field calculator processors.