The Scalability Suggestion warning is issued in the following situations:

You should avoid having screen input parameters of the Binary Data data type.

You should avoid having screen input parameters of the List data type.

You should avoid having screen input parameters whose type is Record and that has a Binary Data, Record, or List attribute.

You should avoid having session variables of the Binary Data data type.

You should avoid having session variables of the List data type.

You should avoid having a session variable of List or Record data type that has an attribute of the Binary Data, Record, or List data type.

You should split the original entity into two entities, placing the Binary Data attribute in one of the entities. The primary key of this entity must be indexed via a foreign key in the original entity.

Open the aggregate to validate whether the join between these two entities is correct. Probably you have a  cross join, while your intention was most likely to make an inner or outer join but you forgot to define this join condition.

You should, due to performance reasons, index the reference attribute of that entity. How?

Check the Start Index and Maximum Iterations properties of your for each and update the properties with the values suggested respectively in '<start index>' and '<maximum iterations>', based on the properties of Table Records widget or the List Records widget: either the value of the LineCount property, if StartIndex is 0, or the value StartIndex + LineCount + 1, otherwise. In this situation, you have the guarantee that you are iterating as many records as you need to display.

Clicking the symbol will take you directly to the element that issued the warning.

See Also

About Input Parameters | Create Relationships | Defining Indexes | About Warning Messages