cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Regular Visitor

Trigger Window Tokens - Collections & Sharepoint

Scenario: I have multiple Collections loading from multiple Sharepoint Lists. I noticed 2 additional columns in my Collections that I have no idea where they're coming from, or had to get rid of them. 

 

Note I use DropColumns already when loading Collections from Sharepoint. However, when I tried adding these 2 random columns to DropColumns, they persist.

 

Specifically - they're named "Trigger Window Start Token" and "Trigger Window End Token".  

 

For what it's worth, I don't have any Flows set up (that I know of).

 

Anyone have any ideas how these columns appeared, what they're related to, and how to get rid of them?

1 ACCEPTED SOLUTION

Accepted Solutions
Super User III
Super User III

Hi @bmort ,

There are a number of other columns similar you will see collecting directly from a SharePoint List (which also you cannot get rid of with DropColumns) - two choices

  • Use ShowColumns for the ones you need
  • Ignore them (which you can do unless you are using Collect back to a list with the Collection).

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

View solution in original post

4 REPLIES 4
Super User III
Super User III

Hi @bmort ,

There are a number of other columns similar you will see collecting directly from a SharePoint List (which also you cannot get rid of with DropColumns) - two choices

  • Use ShowColumns for the ones you need
  • Ignore them (which you can do unless you are using Collect back to a list with the Collection).

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

View solution in original post

Thanks for your reply. I don't see any other columns coming from my SharePoint lists (yet) that I'm unable to get rid of using DropColumns.

 

I understand the first option will likely work, but terribly time consuming as I have 40+ fields for each collection this is happening to (3). Ignoring them seems to be working for now even though I am patching back to the SharePoint lists(s). I did have to modify using Collect to Patch. I just hope that these extraneous columns don't cause me the headache of using ShowColumns for 120+ different fields across 3 Collections 🙂

 

 

 

 

Hi @bmort ,

Have you thought of simply using

Patch(
   YourListName,
   <whatever your ID criteria>
   YourFormName.Updates
)

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

 

Hi @bmort ,

Just checking if you got the result you were looking for on this thread. Happy to help further if not.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Community Highlights

Community Highlights

Check out the Power Platform Community Highlights

Top Solution Authors
Top Kudoed Authors
Users online (7,684)