SOLVED

Inspecting SharePoint News Metadata in Flow

%3CLINGO-SUB%20id%3D%22lingo-sub-332684%22%20slang%3D%22en-US%22%3EInspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332684%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20been%20unable%20to%20find%20a%20way%20to%20inspect%20News%20article%20page%20metadata%20via%20a%20Flow%20action.%20From%20looking%20at%20all%20the%20content%20through%20SharePoint%2C%20it%20would%20seem%20that%20a%20news%20article%20is%20essentially%20just%20a%20regular%20aspx%20page%2C%20but%20with%20a%20%22Promoted%20State%22%20value%20of%202%20instead%20of%200.%20However%2C%20I'm%20unable%20to%20inspect%20this%20data%20within%20Flow.%20Similarly%2C%20I%20can't%20seem%20to%20find%20some%20of%20the%20other%20metadata%20properties%2C%20such%20as%20Author%20Byline%2C%20First%20Published%20Date%2C%20Like%20Count%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20use%20the%20%22Get%20File%20Metadata%22%20action%2C%20it%20only%20seems%20to%20pull%20the%20bare%20bones%2C%20such%20as%20LastModified%2C%20DisplayName%2C%20ID%2C%20Path%2C%20etc.%20Is%20there%20a%20different%20action%20I%20should%20be%20using%20to%20get%20the%20metadata%20I%20want%20(as%20above)%2C%20or%20am%20I%20configuring%20this%20incorrectly%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-332684%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-334542%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-334542%22%20slang%3D%22en-US%22%3E%3CP%3EPerfect%20thanks!%20Turns%20out%20it%20was%20the%20trigger%20which%20was%20causing%20issues.%20I%20was%20using%20%22When%20a%20file%20is%20created%20in%20a%20folder%22%20and%20not%20%22When%20an%20item%20is%20created.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInteresting%20though%2C%20because%20the%20version%20I%20used%20still%20triggered%20correctly%2C%20it%20just%20didn't%20pull%20in%20the%20metadata%20for%20which%20I%20was%20looking.%20Thanks%20for%20the%20help%2C%20you%20solved%20it!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333407%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333407%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20You%20do%20a%20trigger%2C%20whatever%20that%20is%2C%20Then%20get%20file%20properties%20pointing%20to%20same%20Site%20pages%20library.%20Then%20in%20any%20action%20after%20as%20shown%20in%20e-mail%20one%20I%20can%20reference%20it.%20I%20could%20use%20it%20in%20the%20Condition%20action%20as%20well%20by%20adding%20in%20Promoted%20State%20is%20equal%20to%202%20etc.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20665px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F72399iA36EF25A0BE3B432%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22goodnightflow1.jpg%22%20title%3D%22goodnightflow1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F72401i6E66DC029E99E308%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22flow2.jpg%22%20title%3D%22flow2.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333399%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333399%22%20slang%3D%22en-US%22%3EThanks%20I%20appreciate%20that.%20As%20for%20the%20alert%20being%20easier%2C%20yes%2C%20it%20would%20be%2C%20but%20it%E2%80%99s%20not%20scalable.%20I%E2%80%99m%20essentially%20doing%20some%20exploratory%20work%20right%20now%20to%20see%20how%20we%20could%20leverage%20flow%20within%20some%20our%20business%20processes.%20Sending%20an%20email%20is%20just%20one%20example%20use%20case%20here%2C%20but%20as%20I%20learn%20more%20I%20have%20grand%20designs%20to%20do%20more%20%E2%80%94%20but%20it%E2%80%99s%20all%20based%20on%20being%20able%20to%20access%20the%20metadata%20associated%20with%20a%20news%20post%20in%20a%20SitePages%20library.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333397%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333397%22%20slang%3D%22en-US%22%3EIt%20would%20be%20way%20easier%20to%20use%20the%20alert%20me%20function%20in%20the%20menu%20and%20have%20a%20view%20filtering%20the%20alerts.%20Let%20me%20get%20home%20here%20in%20next%2030%20minutes%20and%20I%E2%80%99ll%20do%20a%20vid%20or%20screenshot%20guide%20of%20that%20or%20the%20flow%20method%20for%20you.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333395%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333395%22%20slang%3D%22en-US%22%3EIf%20I%20use%20Get%20File%20Properties%20and%20specify%20SitePages%2F%20it%20still%20doesn't%20work.%20Maybe%20it%20would%20help%20to%20explain%20what%20I'm%20trying%20to%20accomplish...%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20an%20item%20is%20created%20in%20the%20SitePages%20library%20of%20a%20site%2C%20run%20a%20Flow%20which%20first%20checks%20that%20the%20item%20created%20is%20a%20news%20item%20(aka%20Promoted%20State%20%3D%202)%2C%20and%20if%20so%2C%20send%20an%20email%20to%20someone%20which%20outputs%20some%20of%20the%20metadata%20associated%20with%20that%20item%20(author%2C%20publish%20time%20and%20date%2C%20title%2C%20etc).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333394%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333394%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20unfortunately%20a%20bit%20beyond%20my%20expertise%20level%2C%20but%20I%20appreciate%20the%20response.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333383%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333383%22%20slang%3D%22en-US%22%3EOh.%20All%20you%20need%20to%20do%20is%20use%20those%20actions%20and%20manually%20put%20in%20with%20the%20specific%20folder%2F%20library%20and%20the%20in%20%2FSite%20Pages%20and%20it%E2%80%99ll%20let%20you%20access%20it.%20You%20can%E2%80%99t%20select%20it%20out%20of%20the%20list.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333376%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333376%22%20slang%3D%22en-US%22%3ETry%20get%20items%20and%20not%20file%20properties%20as%20it%20is%20still%20a%20list%20item%20as%20a%20base%20type%2C%20if%20that%20doesn't%20work%2C%20use%20the%20Send%20HTTP%20to%20SharePoint%20action%20and%20construct%20the%20REST%20call%20to%20select%20and%20expand%20the%20fields%20you%20need%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333370%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333370%22%20slang%3D%22en-US%22%3E%3CP%3EAppreciate%20the%20help!%20The%20trouble%20I%20have%20with%20that%20is%20using%20the%20Update%20File%20Properties%20or%20even%20Get%20File%20Properties%20can't%20be%20pointed%20at%20the%20SitePages%20library%20--%20only%20the%20default%20Documents%20library%20(but%20that%20library%20doesn't%20contain%20the%20content%20I'm%20looking%20for).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333356%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333356%22%20slang%3D%22en-US%22%3ESo%20get%20file%20properties%20to%20get%20data%20and%20update%20file%20properties%20to%20change%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333353%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333353%22%20slang%3D%22en-US%22%3EDon%E2%80%99t%20think%20it%E2%80%99s%20the%20metadata%20action%20it%E2%80%99s%20the%20properties%20one.%20Been%20awhile%20I%20need%20to%20loon%20myself%20lol%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-333061%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333061%22%20slang%3D%22en-US%22%3E%3CP%3EUnfortunately%20they're%20not%20there%20for%20me.%20Once%20I%20click%20on%20Show%20More%2C%20the%20complete%20list%20I%20get%20is%3A%3C%2FP%3E%3CUL%3E%3CLI%3EDisplayName%3C%2FLI%3E%3CLI%3EETag%3C%2FLI%3E%3CLI%3EFileLocator%3C%2FLI%3E%3CLI%3EId%3C%2FLI%3E%3CLI%3EIsFolder%3C%2FLI%3E%3CLI%3EItemId%3C%2FLI%3E%3CLI%3ELastModified%3C%2FLI%3E%3CLI%3EMediaType%3C%2FLI%3E%3CLI%3EName%3C%2FLI%3E%3CLI%3EPath%3C%2FLI%3E%3CLI%3ESize%3C%2FLI%3E%3C%2FUL%3E%3CP%3ENone%20of%20the%20other%20columns%20show%20up.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-332710%22%20slang%3D%22en-US%22%3ERe%3A%20Inspecting%20SharePoint%20News%20Metadata%20in%20Flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332710%22%20slang%3D%22en-US%22%3ELast%20I%20used%20flow%20on%20this%20it%20worked%20fine%20and%20could%20see%20all%20the%20available%20columns.%20Make%20sure%20you%20are%20clicking%20the%20show%20more%20link%20on%20the%20right%20where%20the%20columns%20list%20out%20they%20usually%20get%20hidden%20in%20there.%3C%2FLINGO-BODY%3E
Occasional Contributor

I have been unable to find a way to inspect News article page metadata via a Flow action. From looking at all the content through SharePoint, it would seem that a news article is essentially just a regular aspx page, but with a "Promoted State" value of 2 instead of 0. However, I'm unable to inspect this data within Flow. Similarly, I can't seem to find some of the other metadata properties, such as Author Byline, First Published Date, Like Count, etc.

 

If I use the "Get File Metadata" action, it only seems to pull the bare bones, such as LastModified, DisplayName, ID, Path, etc. Is there a different action I should be using to get the metadata I want (as above), or am I configuring this incorrectly?

13 Replies
Last I used flow on this it worked fine and could see all the available columns. Make sure you are clicking the show more link on the right where the columns list out they usually get hidden in there.

Unfortunately they're not there for me. Once I click on Show More, the complete list I get is:

  • DisplayName
  • ETag
  • FileLocator
  • Id
  • IsFolder
  • ItemId
  • LastModified
  • MediaType
  • Name
  • Path
  • Size

None of the other columns show up.

Don’t think it’s the metadata action it’s the properties one. Been awhile I need to loon myself lol
So get file properties to get data and update file properties to change

Appreciate the help! The trouble I have with that is using the Update File Properties or even Get File Properties can't be pointed at the SitePages library -- only the default Documents library (but that library doesn't contain the content I'm looking for).

Try get items and not file properties as it is still a list item as a base type, if that doesn't work, use the Send HTTP to SharePoint action and construct the REST call to select and expand the fields you need
Oh. All you need to do is use those actions and manually put in with the specific folder/ library and the in /Site Pages and it’ll let you access it. You can’t select it out of the list.

That's unfortunately a bit beyond my expertise level, but I appreciate the response. :)

If I use Get File Properties and specify SitePages/ it still doesn't work. Maybe it would help to explain what I'm trying to accomplish...

When an item is created in the SitePages library of a site, run a Flow which first checks that the item created is a news item (aka Promoted State = 2), and if so, send an email to someone which outputs some of the metadata associated with that item (author, publish time and date, title, etc).
It would be way easier to use the alert me function in the menu and have a view filtering the alerts. Let me get home here in next 30 minutes and I’ll do a vid or screenshot guide of that or the flow method for you.
Thanks I appreciate that. As for the alert being easier, yes, it would be, but it’s not scalable. I’m essentially doing some exploratory work right now to see how we could leverage flow within some our business processes. Sending an email is just one example use case here, but as I learn more I have grand designs to do more — but it’s all based on being able to access the metadata associated with a news post in a SitePages library.
best response confirmed by Tortilla (Occasional Contributor)
Solution

So You do a trigger, whatever that is, Then get file properties pointing to same Site pages library. Then in any action after as shown in e-mail one I can reference it. I could use it in the Condition action as well by adding in Promoted State is equal to 2 etc. 

goodnightflow1.jpg

flow2.jpg

Perfect thanks! Turns out it was the trigger which was causing issues. I was using "When a file is created in a folder" and not "When an item is created."

 

Interesting though, because the version I used still triggered correctly, it just didn't pull in the metadata for which I was looking. Thanks for the help, you solved it! :)