API Support & FAQ
Via the 'users' API guests are reported as members
Feature request? that "Dashboard Guests" are reported as something other than "members" when querying the API.
Custom data on Members
Per this forum post there (is/was) no way to retrieve custom data on User. Does this mean there is also no way to update custom data on a user?
Access to saved reports in Library via API
The original needs is to identify the linked project for a given task on current timesheets. The API endpoint for timesheets (logged-time-entries/v1) does not include the linked project for the task.
Accessing "reference" field from User profile via API
We are beginning more indepth vetting of LP Next to our existing install. The "reference" field that we are currently using to tie LP users to our ERP/Payroll platform is not being surfaced when we query the /users/v1 api
Missing ID bug has returned
Last year we had an issue with the LP ID column missing from grid downloads which had previously been resolved. However, this issue seems to have returned in the past few days, except now the LP ID column is present but blank for all items. This happens for both API and manual grid view downloads. Please let me know if something has changed or if you need any additional information to help resolve this.
Updating Project Priority
Hello,
Fetch Projects Based on Priority
Hi, I'd like to fetch the projects in the order that they are displayed in liquid planner. When they are created, we usually move them up and down based on priority. Is there a way to do that in the API using some filter or order by command? I tried using "relativePriority" field but it does not have any value.
Fetch items with children
Hi is there a way to fetch the item tree down to a certain depth like in LP Classic (in one GET query)?
I think your API documentation is not generating correctly
The organizations endpoint appears under the "Users" table of content entry
Connecting LiquidPlanner Discussions to Google Chat
We use Google Workspace for our collaboration and productivity tools, including Chat. One of the biggest challenges to embedding LiquidPlanner in daily workflows is that it's separated from that conversation. It's not realistic to expect that it will all migrate to LiquidPlanner Discussions, which means there are two separate spaces, and it's likely LiquidPlanner Discussions will never be the dominant space.