> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/template-architecture/images-in-s-docs/dynamic-image-solutions/placing-images-in-columns.md).

# How to: Place Images in Columns

This page will guide the user through generating a related list and generating images from that related list.

## Prerequisites:

Before proceeding, the user should have:

* The permissions to create and edit S-Docs Templates
* An Object Record with Images store in a related list

## Instructions:

We will showcase this by pulling images from the Files related list on an object record

```html
<table>
	<tbody>
		<tr><!--{{!
<lineitemsSOQL>
<class>none</class>
<soql>select ContentDocument.latestpublishedversionid, ContentDocument.LatestPublishedVersion.pathonclient from contentdocumentlink where  LinkedEntityId='{!ObjectID15}' AND (ContentDocument.LatestPublishedVersion.pathonclient LIKE'%.png%')
</soql>
<column newrow="X" type="rtf" prefix="<td><img src='" postfix="' width='150px'
style='border:2px solid black;' /></td>">ContentDocument.latestpublishedversionid</column>
</lineitemsSOQL>
}}-->
		</tr>
	</tbody>
</table>
```

{% hint style="info" %}
Replace “X” in `newrow="X"` with the number of columns to be displayed.\
`!ObjectId15` can be replaced with the object ID of the related list where the images are being pulled from.
{% endhint %}


---

# 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://help.sdocs.com/sdocs/template-architecture/images-in-s-docs/dynamic-image-solutions/placing-images-in-columns.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.