SQL Source selection and display with id, name and an image

See for reference what I mean:

What is your source table? Please show how it stores the data. There is the name and where is the picture name and so on.

Hi Sergey, thanks for your response.

Things displayed as icons are attractions, activities and amenities and each have their own type (see below).

These types have an Icon field (see below).

With these, I'm using SQL Source queries to add to the Asset creation form via multi-select, check box, etc. (see below).

Now it looks like the selections from above are stored in "js_res_record" in the "fields" column as a combo of the record_id and text name {"5":"Spring","6":"Summer"} etc. (see below).

But the actual images (links) are in "js_res_files". This also seems to include the same record_id as above.

So what I THINK is needed is some kind of join request from the database that lets me pull and display the appropriate icon file from "js_res_files" whenever that icon's record_id is in the asset that is being displayed in an article.

Make sense?

Yes, this make sence. And yes you need concatination and join request if you continue with SQL source.

But you also can use relation field parent/child. It will be easy to attach artilces from other section. Also control how it looks with custom template.

But if you want to continue with SQL query, please show me your query now and I'll try to advaice how to improve it.

Hi Sergey,

I guess I don't understand how parent/child works. Is there documentation about it?

In this case, the items with the icons (attractions, activities, amenities) are a set group determined by the site managers who then assign them to individual locations. They are displayed to, but never edited by, the site viewers.

If Parent/Child will work without reinventing the wheel I'm all for it!

graphxks If Parent/Child will work without reinventing the wheel I'm all for it!

Actualy it should. But I cannot say for sure because I still do not understand vy you store attraction names as a separate articles. Only to attach Icon or you have description and people can browse through attractions.

Sergey But you also can use relation field parent/child. It will be easy to attach artilces from other section. Also control how it looks with custom template.

I was about to suggest the same solution ;) I would choose the parent/child route... because you can reach the same goal by configuration (and templates).

Sergey. Yes, attractions have additional data (description, etc.) attached to them.