The error message indicates that you're trying to send an input parameter (`'item/IssueSource'`) to the `Create_item_2` operation in a workflow, but it expects a value in the format of a `String/uri`, while the provided value `"Human Resources"` is being interpreted incorrectly.
Here’s how to troubleshoot and resolve this issue step by step:
### Understanding the Error
1. **Parameter Format Requirement:**
- The `item/IssueSource` parameter expects a string that conforms to a URI format. This usually means it needs to be a complete URL or a relative path that identifies a specific resource.
2. **Current Input Value:**
- The error occurs because you are passing the value `"Human Resources"` (a plain string) instead of a string formatted as a URI. This is likely causing the conversion issue.
### Steps to Correct the Error
1. **Determine Expected Format:**
- Check the API documentation for the `Create_item_2` operation to confirm what exact format and values are expected for the `IssueSource` parameter.
2. **Modify the Input Value:**
- Change the input value for `item/IssueSource` from `"Human Resources"` to a valid URI. For example, you may need to format it as:
```
"https://example.com/issue-source/human-resources"
```
- Alternatively, if you have a specific value that the API recognizes as valid, use that, like:
```
"Human%20Resources"
```
This encodes spaces into URI-friendly format.
3. **Using expression syntax if needed:**
- If you're dynamically populating this value, ensure it correctly formats into a URI before passing it to the workflow operation. You may use expressions to format it as needed.
### Example Correction for Dynamic Content:
- If you are using Dynamic Content or variables in your workflow, make sure to utilize expressions to format the string. An example expression might look like this:
```plaintext
concat('https://example.com/issue-source/', uriComponent('Human Resources'))
```
- This encodes any special characters in `Human Resources`, ensuring that the output is a valid URI format.
### Additional Considerations
- **Testing**: After making the changes, run the workflow to check if the problem persists. Make sure to monitor the inputs being passed to the `Create_item_2` operation.
- **Debugging**: Use temporary logging or debug methods to print out the final value being sent to the operation to confirm it matches expectations.
### Documentation Links:
- [OpenAPI Specification](https://swagger.io/specification/)
- [Function reference for expressions in Power Automate](https://learn.microsoft.com/en-us/power-platform/guidance/coe/expression-functions)
🏷️ Tag me if you have any further questions or if the issue persists.
✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.
❤️ Give it a Like if you found the approach useful in any way.
