Some users find that their JSON requests have metadata only at the root,
expecting that the decision service can infer the metadata for subordinate levels.
That tactic is now supported, although the output provides the metadata at all
levels. The following example shows the coupons
Ruletest in the advanced tutorial. It executes as expected with either request, and
produces identical responses (both with metadata).
How to: Use Simplified JSON in requests
Copy the request you want to simplify to an editor.
Add the decision service name as
name at the top.
Delete (or leave out) the metadata for related entities.
Retain the metadata for the primary entity.
For example:
Note
In the example, Name at the
bottom is an attribute of the root entity.
Mind your commas, braces, and brackets when you are paring down a
known-good request.
