JSON Data

I'm trying to understand how to handle an ASM policy that appears to be finding JSON data and not handling it properly. The person who set up the policy using the wizard didn't check the box for JSON data, so we may have to simply reconfigure the policy and lose what we've learned so far, but I'm hoping there's a different way to handle it.

But the bigger question is whether I'm even on the right track, and what will happen once we set up the JSON profile. I'm attaching a sample of what the data looks like, and it's clearly an address array, but it's incomplete in the sense that it hasn't grabbed everything through the final closing bracket. Since these are addresses, it's extremely unlikely there will be actual duplicates, which is I suppose why ASM is identifying this as an illegal parameter. I can create a JSON profile and tell ASM to use the JSON profile for these entries, but I'm not sure what the long-term effects of that will be -- whether that will result in similar (but not duplicate) entries not being identified as not being illegal parameters.

Any comments or suggestions? Thanks.