> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.206/help-center-index/troubleshooting-index/errors-index/tfs-error-solutions/oh-tfs-azure-devops-0169.md).

# OH-TFS/AzureDevOps-0169

### Description

When you encounter OH-TFS/Azure DevOps-0169 then the following error messages will appear:

"OH-TFS/Azure DevOps-0169: Create or Update entity of type `<Entity_Type>` for `<Project_Name>` project is failing. Error received from the server: Failed to create/update entity because : InvalidEmpty for field \[`<Field>`] value \[`<Value>`]".

### Cause

Following are the probable reasons for this:

* Mandatory fields have not been configured while doing field configuration.
* Invalid value is being written in `<Field>`, which is not acceptable by Team Foundation Server (TFS)/Azure DevOps.

### Solution

* You need to configure all the fields which are mandatory from Team Foundation Server (TFS)/Azure DevOps Interface while configuring mapping for integration.
* In case you have mapped non-mandatory source field with Mandatory target field, then you can provide [Default Mapping](/v7.206/integrate/configure-integrations/mapping-configuration.md#default-mapping) for that field.
* If any rule is configured in Team Foundation Server (TFS)/Azure DevOps interface that prevents invalid values to be written in the fields then you need to do field mapping accordingly. Here also you can provide [Default Mapping](/v7.206/integrate/configure-integrations/mapping-configuration.md#default-mapping) for the field for which error is coming.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opshub.com/v7.206/help-center-index/troubleshooting-index/errors-index/tfs-error-solutions/oh-tfs-azure-devops-0169.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.