cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Custom Planner Connector to update the bucketId on a task: how to set the If-Match request parameter?

Hi.

In my PowerApp using the standard connector I can update the Task Title of the current record in the Gallery eg

 

onChange = Planner.UpdateTaskV2(id,{title:TaskTitle.Text})

 

 ie in the onChange event handler of the Text component called "TaskTitle", call the Planner connector method UpdateTaskV2(id,{title:TaskTitle.Text}) and yes, the Task Title updates in Planner. Same for updating the dueDateTime:

 

Planner.UpdateTaskV2(id,{dueDateTime:dueDate})

 

So far so good. Now, what I also want to do is update the bucketId to move a Task record from one bucket in the plan to another which the standard connector does not allow. So, I need to make a Custom Connector (CC).

I made a CC called PlannerCustomConnector (imaginative, I know!) with a bunch of GETs and all works well. eg for a Gallery Items collection:

 

PlannerCustomConnector.ListBucketTasks("myBucketIdGoesHere").value

 

To change the bucketId on a Task I need to use PATCH with an If-Match of the most recent etag from the Task. Testing that in MSGraph works to shift the Task record from one bucket to another eg:

 

PATCH https://graph.microsoft.com/v1.0/planner/tasks/myTaskIdHere
Request header If-Match : W/"JzEtVGFzayAgQEBAQEBAQEBAQEBAQEBESCc="   
Request body: { "bucketId":"theTargetBucketIdInThisPlanGoesHere" }

 

where that If-Match was copied from the etag of the most recent GET of that same task. So, that much works.

 

Now, what I cannot work out is how to define the PATCH request in the PowerApps Custom Connector builder so I can set the If-Match request header property. I can get the etag data from ThisItem in the app, of course, but how to define the request in the Connector so I can set the request header property with that value? Or so it will do it for me even?

I used the Postman => Export => import to PowerApps Connector method for all my other requests and have a definition item for my UpdateTask request in the PowerApps Connector builder but what value do I put in the Request Header CC definition for the If-Match key??

 

This is the last hurdle preventing me from finishing my custom Planner app. Well, I hope it is the last hurdle anyway - I have said that about 10 times so far in this project! So many Gotchas!

Thanks,

Murray

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

Sorry for the delay getting back. I now have this working.

So, in addition to the helpful info above there was another request header that was required to make this useful in an app and which is not mentioned in the docs. 😞

Here are the steps to define an action called UpdateTask:

1. This blog post outlines setting up the Azure App permissions etc so your custom connector can authenticate on behalf of the user who is using it (ie you, for now).

https://toddbaginski.com/blog/how-to-make-a-custom-connector-for-powerapps-and-flow-that-calls-the-m... 

Follow that pattern to delegate permissions, generate the secret key, etc. That blog post example requires Directory and Group permissions. For Planner you will also need to delegate permissions for Tasks eg Tasks.ReadWrite (and possibly others depending on what you want your custom connector to be able to do). 

2. In the Generate Swagger file section, when using Postman, add API calls for the various Planner calls you want to include in your connector. In terms of this example, we will want one for at least GetTask and UpdateTask

 

 

 

 

GET https://graph.microsoft.com/v1.0/planner/tasks/:taskid
PATCH https://graph.microsoft.com/v1.0/planner/tasks/:taskid

 

 

 

 

Note that with some extra work you can use Postman to test your calls, that is not necessary here. All we are doing is defining the API calls we want to build into our custom connector so Postman will build the JSON definition file for us. So, add your calls and continue down to Export your collection of API calls.

3. Follow the instructions in the Create your custom connector section of the blog post.

Build the action for GetTask() first. It is simple and you can use it to make sure all is working before going on to define the UpdateTask() action. Note that in the blog post Todd is using the connector Test tab to get the template JSON to continue with the definition (step 20 or so). In practice, I found it easier to have the Graph Explorer open in another browser window and use it to run the calls in order to get the template / sample response JSON we need for the connector definition. 

Once you have built and saved the GetTask() action you can test it to make sure you are on track so far. If you wanted you could go ahead and test it in your Power App as per the blog post.

NB: whenever you change your custom connector definition, you will need to remove it from your Power App connectors section and add it back again so the Power App uses the latest version of your connector.

 

Now the UpdateTask() action:

Caveat: This example shows you how to update the simple types (title, bucketId, dueDateTime, etc). I have not tested using it for the objects like assignments{} or createdBy{}

 

Click the Definition tab:

Greenshot 2019-12-17 08.54.19.png

 

Click the UpdateTask action from your Postman import (as above). Fill in the dialog:

Greenshot 2019-12-18 21.15.12.png

 

Scroll down to Import from sample and click it then add the following (text samples are below the image), then click Import:

Greenshot 2019-12-17 09.46.17.png

 

 

https://graph.microsoft.com/v1.0/planner/tasks/{taskid}

If-Match XXXX
Prefer return=representation
{
    "bucketId": "",
    "orderHint": "",
    "assigneePriority": "",
    "title": "",
    "percentComplete": 0,
    "startDateTime": null,
    "dueDateTime": "",
    "conversationThreadId": null,
    "appliedCategories": {},
    "assignments": {}
}

 

 

Notes on the above:

1. Only the header property names are used. Their values don't matter here.

2. Same for the Body definition / template (hence empty property values). This fragment contains the full list of possible properties one can change according to the Graph docs at the time of writing (December 2019). At some stage the priority property will come out of Beta. When it does we will need to update this connector by adding that to the JSON (or start using the Beta url now, not recommended). If your connector only needs a subset of properties that you wish to make updateable, only specify the ones you need in the JSON.

Scroll down to the Headers section and Edit the If-Match:

Greenshot 2019-12-17 09.49.13.png

set its values like so, then click the Back button to save your changes:

Greenshot 2019-12-17 09.52.23.png

Same for Prefer.

Greenshot 2019-12-17 09.53.31.png

NOTE: the Default value is set because we want to use that on all calls. It is not dynamic and we do not want to have to pass it on every UpdateTask() action (unlike the If-Match header value) so we set the default and set visibility to "Internal". Don't quote me on that explanation but these settings work.

The purpose of the Prefer header with this value is to tell Graph to return the updated Task record. This is not mentioned in the docs but is vital so we get back an updated odata.etag value so we can do subsequent updates on the same record.

See: https://docs.microsoft.com/en-us/graph/api/resources/planner-overview?view=graph-rest-1.0#planner-re... 

 

Now define the Response Body, then click Import.

Greenshot 2019-12-17 10.12.11.png

Again, the JSON values do not matter, just the property names. To get the JSON, use Graph Explorer to run a Get Task query and copy the response JSON

 

 

https://graph.microsoft.com/v1.0/planner/tasks/{task-id}

 

 

Finally, update your connector.

Greenshot 2019-12-17 10.13.13.png

Now you can use your custom connector in your Power App. eg in a Gallery template definition for a Task. I have a dropdown control (called "bucket") on each Task record the gallery collection that lists the the buckets on that Plan so the user can use the dropdown to move a task from one bucket to another within that Plan. 

This is a simplified version. There is a bit more to this in practical application - the subject of another post.

 

 

Items = PlannerCustomConnector.ListPlanBuckets("my plan id here").value
onChange = PlannerCustomConnector.UpdateTask(id,'@odata.etag',{bucketId: bucket.Selected.id})

 

 

The take-away here is that the parameter list to UpdateTask() is the taskId AND the If-Match header value (the current etag of ThisItem's Task record) AND the object containing the data to change (the bucketId of the selected item in the bucket dropdown).

Similarly, to update the Task Title:

 

 

onChange = PlannerCustomConnector.UpdateTask(id,'@odata.etag',{title: TaskTitle.Text})

 

 

where TaskTitle is the control property name of the title field on the gallery item template.

IMPORTANT: at this point the connector should successfully update the server ONCE, but subsequent updates might fail, depending on how you set up your gallery collection. This relates to keeping track of the updated etag that is sent back after each call to UpdateTask(). I do have a work around and lots of questions about that which I will point to once I fully understand the best way forward.

Cheers,

Murray

 

 

View solution in original post

5 REPLIES 5
v-xida-msft
Community Support
Community Support

Hi @Anonymous ,

Could you please share a bit more about your scenario?

Do you want to set a "If-Match" HTTP Request header property within your app when you executing the PlannerCustomConnector.UpdateTask() action?

 

If you want to set a "If-Match" HTTP Request header property within your app when you executing the PlannerCustomConnector.UpdateTask() action, I have made a test on my side, please consider take a try with the following workaround:

1. Define your "UpdateTask" action within your custom connector as below:

1.JPG

Note: The action patch (/v1.0/planner/tasks/{taskId}) is based on the Base URL you specified in your custom connector. If you specified /v1.0 as your Base URL, the above action path should be changed into /planner/tasks/{taskId}.

2. Edit the "If-Match" header within your operation as below:

2.JPG

3. Edit the If-Match Header as below:

3.JPG

4. Then click "Back" button, and specify proper Body Response Payload for this operation.

5. Save your custom connector.

 

Then when you executing the PlannerCustomConnector.UpdateTask() action within your app, the "If-Match" header property would be marked as Required property, there you could provide a proper value for it using ThisItem.ETag formula.

4.JPG

 

Please take a try with above solution, check if the issue is solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Thank you! I will work on this later today and report back.

Much appreciated.

Murray

Hi @Anonymous ,

Have you taken a try with the solution I provided above? Have you solved your problem?

 

If you have solved your problem, please consider go ahead to click "Accept as Solution" to identify this thread has been solved.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Yes I will set as accepted once I have fully tested. Your post was a great start but there was more to it which I am still working through. One thing is that you MUST also send the following request header item (in addition to the If-Match) otherwise you do not get data back and usually get an error instead. This is not in the docs.

Prefer: return=representation

Once I have a complete working replacement for the UpdateTask() method in my custom connector I will update this post with full instructions. That will be in a few days.

Thanks,

Murray

Anonymous
Not applicable

Sorry for the delay getting back. I now have this working.

So, in addition to the helpful info above there was another request header that was required to make this useful in an app and which is not mentioned in the docs. 😞

Here are the steps to define an action called UpdateTask:

1. This blog post outlines setting up the Azure App permissions etc so your custom connector can authenticate on behalf of the user who is using it (ie you, for now).

https://toddbaginski.com/blog/how-to-make-a-custom-connector-for-powerapps-and-flow-that-calls-the-m... 

Follow that pattern to delegate permissions, generate the secret key, etc. That blog post example requires Directory and Group permissions. For Planner you will also need to delegate permissions for Tasks eg Tasks.ReadWrite (and possibly others depending on what you want your custom connector to be able to do). 

2. In the Generate Swagger file section, when using Postman, add API calls for the various Planner calls you want to include in your connector. In terms of this example, we will want one for at least GetTask and UpdateTask

 

 

 

 

GET https://graph.microsoft.com/v1.0/planner/tasks/:taskid
PATCH https://graph.microsoft.com/v1.0/planner/tasks/:taskid

 

 

 

 

Note that with some extra work you can use Postman to test your calls, that is not necessary here. All we are doing is defining the API calls we want to build into our custom connector so Postman will build the JSON definition file for us. So, add your calls and continue down to Export your collection of API calls.

3. Follow the instructions in the Create your custom connector section of the blog post.

Build the action for GetTask() first. It is simple and you can use it to make sure all is working before going on to define the UpdateTask() action. Note that in the blog post Todd is using the connector Test tab to get the template JSON to continue with the definition (step 20 or so). In practice, I found it easier to have the Graph Explorer open in another browser window and use it to run the calls in order to get the template / sample response JSON we need for the connector definition. 

Once you have built and saved the GetTask() action you can test it to make sure you are on track so far. If you wanted you could go ahead and test it in your Power App as per the blog post.

NB: whenever you change your custom connector definition, you will need to remove it from your Power App connectors section and add it back again so the Power App uses the latest version of your connector.

 

Now the UpdateTask() action:

Caveat: This example shows you how to update the simple types (title, bucketId, dueDateTime, etc). I have not tested using it for the objects like assignments{} or createdBy{}

 

Click the Definition tab:

Greenshot 2019-12-17 08.54.19.png

 

Click the UpdateTask action from your Postman import (as above). Fill in the dialog:

Greenshot 2019-12-18 21.15.12.png

 

Scroll down to Import from sample and click it then add the following (text samples are below the image), then click Import:

Greenshot 2019-12-17 09.46.17.png

 

 

https://graph.microsoft.com/v1.0/planner/tasks/{taskid}

If-Match XXXX
Prefer return=representation
{
    "bucketId": "",
    "orderHint": "",
    "assigneePriority": "",
    "title": "",
    "percentComplete": 0,
    "startDateTime": null,
    "dueDateTime": "",
    "conversationThreadId": null,
    "appliedCategories": {},
    "assignments": {}
}

 

 

Notes on the above:

1. Only the header property names are used. Their values don't matter here.

2. Same for the Body definition / template (hence empty property values). This fragment contains the full list of possible properties one can change according to the Graph docs at the time of writing (December 2019). At some stage the priority property will come out of Beta. When it does we will need to update this connector by adding that to the JSON (or start using the Beta url now, not recommended). If your connector only needs a subset of properties that you wish to make updateable, only specify the ones you need in the JSON.

Scroll down to the Headers section and Edit the If-Match:

Greenshot 2019-12-17 09.49.13.png

set its values like so, then click the Back button to save your changes:

Greenshot 2019-12-17 09.52.23.png

Same for Prefer.

Greenshot 2019-12-17 09.53.31.png

NOTE: the Default value is set because we want to use that on all calls. It is not dynamic and we do not want to have to pass it on every UpdateTask() action (unlike the If-Match header value) so we set the default and set visibility to "Internal". Don't quote me on that explanation but these settings work.

The purpose of the Prefer header with this value is to tell Graph to return the updated Task record. This is not mentioned in the docs but is vital so we get back an updated odata.etag value so we can do subsequent updates on the same record.

See: https://docs.microsoft.com/en-us/graph/api/resources/planner-overview?view=graph-rest-1.0#planner-re... 

 

Now define the Response Body, then click Import.

Greenshot 2019-12-17 10.12.11.png

Again, the JSON values do not matter, just the property names. To get the JSON, use Graph Explorer to run a Get Task query and copy the response JSON

 

 

https://graph.microsoft.com/v1.0/planner/tasks/{task-id}

 

 

Finally, update your connector.

Greenshot 2019-12-17 10.13.13.png

Now you can use your custom connector in your Power App. eg in a Gallery template definition for a Task. I have a dropdown control (called "bucket") on each Task record the gallery collection that lists the the buckets on that Plan so the user can use the dropdown to move a task from one bucket to another within that Plan. 

This is a simplified version. There is a bit more to this in practical application - the subject of another post.

 

 

Items = PlannerCustomConnector.ListPlanBuckets("my plan id here").value
onChange = PlannerCustomConnector.UpdateTask(id,'@odata.etag',{bucketId: bucket.Selected.id})

 

 

The take-away here is that the parameter list to UpdateTask() is the taskId AND the If-Match header value (the current etag of ThisItem's Task record) AND the object containing the data to change (the bucketId of the selected item in the bucket dropdown).

Similarly, to update the Task Title:

 

 

onChange = PlannerCustomConnector.UpdateTask(id,'@odata.etag',{title: TaskTitle.Text})

 

 

where TaskTitle is the control property name of the title field on the gallery item template.

IMPORTANT: at this point the connector should successfully update the server ONCE, but subsequent updates might fail, depending on how you set up your gallery collection. This relates to keeping track of the updated etag that is sent back after each call to UpdateTask(). I do have a work around and lots of questions about that which I will point to once I fully understand the best way forward.

Cheers,

Murray

 

 

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Top Solution Authors
Top Kudoed Authors
Users online (5,676)