SUMMARY:
This Technical Note describes a known behavior in Strategy Web 9.4.1-10.x that causes prompt values not to be passed to a Datamart Report that is executed from a URL API. If no prompt values are passed, the user will be shown a page to run the report manually from the Strategy Web 9.4.1-10.x interface, which successfully writes the data back to the table specified for the Datamart.
SYMPTOM:
A Datamart report that runs successfully from Strategy Developer 9.4.1-10.x will not be able to write back data to the table if that same Datamart is called from a URL API that includes prompt value answers in Strategy Web 9.4.1. The user must remove the "&valuePromptAnswers=" parameter, manually answer the prompts, and execute the Datamart from the Strategy Web 9.4.1 interface in order for information to be sent back to the table.
STEPS TO REPRODUCE:
To see the behavior of Datamarts called by URL API described in this technical note, take the following steps in Strategy Tutorial:

&valuePromptAnswers=1%2F10%2F2010^1%2F16%2F2010



CAUSE:
This is a known limitation in Strategy Web 9.4.1-10.x when using URL API to execute special reports such as Datamart report with prompts.
WORKAROUND:
Add an extra parameter("execFlags=83886464") in the URL API to get the correct result, like: "<URL API for the Datamart report>&valuePromptAnswers=1%2F10%2F2010^1%2F16%2F2010&execFlags=83886464" to workaround the issue.
Note: The "execFlags=83886464" only applies to Datamart reports, and is generated by four flags defined in EnumDSSXMLExecutionFlags.java. Users can find the definition in https://www2.microstrategy.com/producthelp/Current/WebAPIReference/com/microstrategy/webapi/EnumDSSXMLExecutionFlags.htm.
public static final int DssXmlExecutionUseCache = 0x00000080;
public static final int DssXmlExecutionUpdateCache = 0x00000100;
public static final int DssXmlExecutionCheckWebCache = 0x01000000;
public static final int DssXmlExecutionGenerateDatamart = 0x04000000;
To execute other special reports using URL API, users need to replace the 4th flag to the corresponding values.
ACTION:
This issue was reviewed by our Technology team for feasibility and will not be scoped for a code fix in any upcoming Strategy release.