Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/ProjectEditor-StructureSection.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,14 @@ Here, you can define a subset of your physical structure to replicate for mobile
* tables will be automatically added to the tabs of your app.
* fields will be available later when it's time to define your list and detail forms.



### Why didn't you select the ID field in the screenshot, above?

You only need to choose fields that your users will see. If your app's users are not going to use the **ID** field, then you do not need to include it. **4D For Mobile** will keep track of it, for you, behind the scenes.



## Many to One relations

* 4D 17R5 allows you to visualize table relations in the generated app publishing them from the Structure section. Then when your related fields are published, they can be used like any other field in the [app creation process](many-to-one-relations.html).
Expand Down Expand Up @@ -88,4 +96,4 @@ From iPhone settings, you can now reset your app data and find information about

> **NOTE**
>
> As soon as the admin performs an important maintenance operation, he shall alert 4D for iOS app users that a Full reload is required: Recover by tag / Restoration / Compaction
> As soon as the admin performs an important maintenance operation, he shall alert 4D for iOS app users that a Full reload is required: Recover by tag / Restoration / Compaction