That works fine for all libraries without the lookup column threshold - (12/14 lookup columns in a view) where get properties action is errored. To avoid that I need to use exact view which is not using so many lookups. Because I am using variables in site address and library name I am not able to choose anything in the Limit Columns in a view section. How can I sort this out and use variable for a particular view?
Are you saying when you go to select a view under "Limit Columns by View," you see no options or that you do not want to use this method?
If you don't see any options, that would not make sense as every list has to have a least one view and there should always be the "Use all columns (Do not limit)" option when it will not exceed the threshold limit.
When I have encountered this issue, I usually do one of two things:
Review the columns in the list to see if they're really needed and delete unnecessary ones until it gets under the threshold limit. I will not get into too much detail, but sometimes a list might have fields for approver, approval date, approval outcome, approval comments. In most instances when I encounter this, I consolidate this information into approval outcome that is multiple lines of text. The biggest cause of this issue is from having a lot of people fields in your list.
If I cannot delete any fields, then I will create multiple views in my list. The trigger will use one view that works to bring the number of fields returned under the threshold. Then when flow is triggered, I use a Get item action based on the ID of the trigger and choose another view that contains the rest of the fields. You just need to be careful when choosing the values from the dynamic content in your flow.
I have only used the HTTP Get request to get specific columns when I don't want users to be able to see data in views without having to open the item. Therefore, I don't know if the HTTP get method will have the same issue regarding the threshold. With this method you should be able to create variables and use those in URI line.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.