# Object Store

The *Object Store* service can be considered a service type only for storing MobiusFlow objects. It has no functional backend. This means, unlike most other MobiusFlow services, the service will not interact with the objects stored on it.

## Uses

* For storing non-service specific objects such as the *Numeric Value* objects or *String Value* objects (Often these will be used if values are being calculated based on other objects)
* Manually writing to an object type, instead of relying on its functional parent service (e.g. manually writing the data into a LoRaWAN device object from the Flows, instead of using the *LoRaWAN LNS* service)
* Testing
* Diagnostics

<figure><img src="/files/tog0jdOKb6AXCSAzXIE0" alt=""><figcaption><p>An example Numeric Value object residing on an Object Store Service</p></figcaption></figure>

## Limitation

Although it is possible to place any object type in an *Object Store* service, because the service has no functional backend, it cannot interact with most object types in fully functional way. For example, adding a LoRaWAN device object to an *Object Store* service is possible, however the object will not be automatically populated by incoming LoRaWAN messages. If the LoRaWAN device object was placed into its functional parent service (*LoRaWAN LNS* service / *LoRaWAN Devices* service) instead, it would function as normal, as these service types have the correct backend to work with this object type.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mobiusflow.com/help/technical-docs/mobiusflow-services/object-store.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.