I recently discovered a limitation with creating a pricing condition table.  I never ran into this before, because I typically haven’t run into much automated pricing for service (usually it’s made up on the fly.  ha ha )  Or typically, just time and material with a markup.  Well, I was attempting to create a pricing table with 13 key fields.  YIKES!  But when I attempted to activate it, I kept getting the following error:

ERROR: VK709 Activation was interrupted

Well, it turns out that you can have a maximum of 11 fields when creating a new condition table.  Luckily, I found a way to combine what I needed (or overall, a better approach), but be aware of how complex you choose to go with your pricing.

Thanks for reading,