<p>Records <em>can</em> do that too (where that = hold data), but, according to <a href="http://buildwithcraft.com/docs/plugins/records" rel="nofollow">Craft docs</a>, Records should never ever leave Service layer. So, yes, you do need a model too.</p>

CC BY-SA 3.0
2015-05-01T14:14:04.883Z
+1 Records should never make their way to a view / template.
Jay
CC BY-SA 3.0
2014-08-28T19:03:29.783Z
2014-08-28T19:03:29.783Z
Andris Sevcenko
<p>I have a record so I can save my data to the DB but do I need a model for services and stuff ? Or can the record do that too ?</p>

<plugin-development><records><models>
Do I need a model when I have a record?
# Do I need a model when I have a record?

(Asked by: username_0 on 2014-08-28)

I have a record so I can save my data to the DB but do I need a model for services and stuff ? Or can the record do that too ?

**Tags:** plugin-development, records, models


---

## 1 answers

### Answer by username_1 on 2014-08-28. Score: 4

Records *can* do that too (where that = hold data), but, according to [Craft docs](http://buildwithcraft.com/docs/plugins/records), Records should never ever leave Service layer. So, yes, you do need a model too.

> **Comments:**
> **username_2**: +1 Records should never make their way to a view / template.  

---

