logo
search
Others

Understanding Power Apps Component Custom Property Limits

Steve KSteve K Oct 13, 2026 868 views

Question details

The user is looking for guidance on the maximum number of custom properties supported by Power Apps components, specifically when dealing with a large volume of inputs.

Understanding Power Apps Component Custom Property Limits
Product
Microsoft Power Apps
Device & OS
not provided
Scenario
Designing a complex Power Apps component that requires a significant number (e.g., over 100) of input properties to function.
Observed behavior
Creating dozens of separate input properties becomes impractical, prompting the need for structural workarounds or official limits clarification.
Before you start

Before adding numerous properties to a single component, evaluate your data architecture to see if related inputs can be logically grouped together to simplify the design.

Solution 1Recommended

Group Related Values into Records or Collections

Optimize your component architecture by consolidating multiple individual input properties into a single structured Record or Table data type.

Creating over 100 separate input properties for a single component is often impractical and can degrade app performance. Instead of passing individual strings or numbers, you can bundle related data into structured formats.

1
Identify related properties

Review your component's input requirements and find fields that share a context, such as user details (Name, Age, Email) or address lines.

2
Create a Record property

In the component's custom property settings, create a new input property and set its Data type to 'Record' or 'Table' instead of standard Text or Number.

3
Pass structured data

When using the component in your app, pass a single record (e.g., {Name: "John", Age: 30}) to this property, effectively replacing multiple individual properties with just one.

Group Related Values into Records or Collections
Performance Boost: Grouping properties into records not only bypasses practical property limits but also makes your component easier to manage and faster to load.
Free Microsoft Office alternative

Discover WPS Office for Your Document Needs

While you build your applications in Power Apps, WPS Office is the perfect lightweight alternative for all your daily document, spreadsheet, and presentation needs. Enjoy full compatibility with Microsoft Office formats at zero cost.

  1. 1. Download the software: Visit the official WPS website and download the free installation package for your operating system.
  2. 2. Install WPS Office: Run the installer and follow the on-screen instructions to set up the lightweight office suite on your device.
  3. 3. Open your existing files: Launch WPS Office and open your .docx, .xlsx, or .pptx files directly without losing any formatting.
Fully compatible with Microsoft Office formats (Word, Excel, PowerPoint)Free, lightweight, and fast-loading alternative to Microsoft 365Familiar user interface ensuring seamless migration and zero learning curveBuilt-in AI tools to help you draft documents and analyze data efficiently
QA img-9

Frequently Asked Questions

Is there a hard limit on custom properties in a Power Apps component?

While Microsoft does not strictly document a hard numerical limit for custom properties, having over 100 properties is widely considered impractical and can lead to severe performance degradation and authoring lag.

How can I reduce the number of input properties needed?

You can significantly reduce the number of inputs by using Record or Table data types. This allows you to group related fields together and pass them as a single structured object rather than dozens of separate strings or numbers.

Where can I get expert help on complex Power Apps component designs?

The best place to find specialized architectural guidance is the official Microsoft Power Apps Community forums, where product experts and engineers frequently answer complex design queries.