> For the complete documentation index, see [llms.txt](https://coldbox-orm.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox-orm.ortusbooks.com/v5.x/base-orm-service/service-methods/creation-population/new.md).

# new

Get a new entity object by entity name. You can also pass in a structure called `properties` that will be used to populate the new entity with.

The entity is created, autowired by WireBox (if entity injection is enabled), populated and then the `ORMPostNew` interception is announced (when `eventHandling` is enabled).

{% hint style="warning" %}
**Changed in cborm 6**: `ORMPostNew` is announced **once** per `new()` call, after the entity is autowired and populated. A plain `entityNew()` also autowires the entity and announces `ORMPostNew` now, through the cborm event handler, but it does not populate it.
{% endhint %}

## Returns

* This function returns the newly created entity

## Arguments

| Key                  | Type    | Required | Default | Description                                                                         |
| -------------------- | ------- | -------- | ------- | ----------------------------------------------------------------------------------- |
| entityName           | any     | true     | ---     |                                                                                     |
| properties           | struct  | false    | {}      | A structure of name-value pairs to populate the new entity with                     |
| composeRelationships | boolean | false    | true    | Automatically attempt to compose relationships from the incoming properties memento |
| nullEmptyInclude     | string  | false    | ---     | A list of keys to NULL when empty                                                   |
| nullEmptyExclude     | string  | false    | ---     | A list of keys to NOT NULL when empty                                               |
| ignoreEmpty          | boolean | false    | false   | Ignore empty property values on populations                                         |
| include              | string  | false    | ---     | A list of keys to include in the population from the incoming properties memento    |
| exclude              | string  | false    | ---     | A list of keys to exclude in the population from the incoming properties memento    |
| ignoreTargetLists    | boolean | false    | false   | Ignore target lists during population                                               |

## Examples

```javascript
// return empty post entity
var post = ormService.new("Post");
var user = ormService.new(entityName="User",properties={firstName="Luis", lastName="Majano", age="32", awesome=true});
var user = ormService.new("User",{fname="Luis",lname="Majano",cool=false,awesome=true});
```


---

# 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://coldbox-orm.ortusbooks.com/v5.x/base-orm-service/service-methods/creation-population/new.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.