Hello Community,
We are trying to import a complex, custom flow solution (MMA_Processing_Core) that requires Environment Variables for scalability. We are hitting a persistent, structural error when deploying the solution ZIP.
The core issue is a missing metadata tag, even though the flow logic itself is correct.
### 🛑 Error Received on Import
The import fails at the "Workflow" component with this precise detail:
"Required property 'schemaVersion' not found in JSON. Path '', line 1, position 3508."
### 🛠️ Flow Architecture
The flow (MMA_Processing_Core) is built for robustness and includes the following complex logic:
1. **Trigger:** Manually trigger a flow (with inputs: Meeting_ID, Raw_Transcript, Style_Instruction).
2. **Context Fix:** The flow uses the **HTTP translateExchangeIds** call to convert a problematic EWS ID to a REST ID, followed by **Get event (V3)**.
3. **LLM Call:** Uses the **AI Builder / Generate key phrases** action to process a custom Master Prompt and return structured JSON.
4. **Delivery:** Uses Parse JSON, Send Email, and a Planner Task creation loop.
### ➡️ Steps Taken (Why Manual Fixes Failed)
We believe the error is due to the compiler not injecting the necessary `clientdata` and `schemaVersion` tags into the flow definition JSON file. We have attempted the following manual fix which still failed:
1. **XML Fix:** We manually ensured the `<EnvironmentVariables>` block was correctly structured in `customizations.xml` with placeholders.
2. **Code Injection:** We replaced the entire content of the flow definition JSON file with the correct robust flow logic.
**Question:**
**What is the minimum JSON or XML structure required, or what specific attribute must be added to the flow definition JSON or the solution's `customizations.xml` file to satisfy the compiler's demand for the `schemaVersion` and `clientdata` properties, thereby allowing the successful import of the solution?**
Thank you for your assistance.
Share
Report
All responses (
Answers (
411
