{"id":13937,"date":"2018-05-08T07:40:04","date_gmt":"2018-05-08T07:40:04","guid":{"rendered":"https:\/\/kb.sambapos.com\/?p=13937"},"modified":"2018-07-05T11:25:34","modified_gmt":"2018-07-05T11:25:34","slug":"9-1-2-creating-custom-reports-with-sql","status":"publish","type":"post","link":"https:\/\/kb.sambapos.com\/en\/9-1-2-creating-custom-reports-with-sql\/","title":{"rendered":"9.1.2. Creating Custom Reports with SQL"},"content":{"rendered":"

Adding SQL Scripts<\/h2>\n
\n

You can display result of an SQL Script in custom reports. If SQL Scripts returns a single value you can use it as a cell value. If it returns multiple values that will be formatted as a table row. In other words SQL result will be converted to a list where each line contains\u00a0|<\/code>\u00a0delimited cell values. So custom report engine can display them as table rows.<\/p>\n<\/div>\n

Creating an SQL script<\/h2>\n
\n

Tip;<\/span>\u00a0In this section samples won’t be real SQL scripts. It will be just shown how you can display SQL results in custom reports.<\/p>\n

Navigate to\u00a0Management > Automation > Scripts<\/code>\u00a0to create a new script.<\/p>\n

\"\"<\/p>\n

Select 5+3<\/code>\u00a0script returns the result of calculation.<\/p>\n

Tip;<\/span>\u00a0Handler<\/code>\u00a0is the name that will be referenced from reports. It should start with `@@` and should not contain spaces.<\/p>\n

Tip;<\/span>\u00a0The reason for creating SQL Scripts outside reports is making\u00a0 scripts reusable so that they can be accessed from multiple reports.<\/p>\n

After saving it you can access this script from custom report by using\u00a0@@Handler_Name<\/code>\u00a0syntax. For this example\u00a0@@SQL1<\/code>\u00a0will display the result of the (5+3) calculation in reports.<\/p>\n

\"\"<\/p>\n

In the template we have this section.<\/p>\n\n\n\n
\n
[SQL Results:1,1]\r\nValue1|@@SQL1     >>> @@SQL1 cell value replaces with the result of 5+3 calculation.<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Since example table have 2 columns, it is possible to return 2 values as the result of\u00a0@@SQL1<\/code>\u00a0and use it as a row.<\/p>\n
\"\"<\/p>\n
It has been added another expression to SQL script so it will return a single row with two columns. As it returns multiple values you can use it as whole row. SambaPOS will automatically convert result to a\u00a0|<\/code>\u00a0delimited row as\u00a0Value|Value2<\/strong>.<\/p>\n
\"\"<\/p>\n
A Real Life Example<\/h2>\n
\n
This script displays ticket counts by peak hours.<\/p>\n
\"\"<\/p>\n\n\n\n
\n
SELECT<\/span> CONVERT<\/span>(<\/span>nvarchar(<\/span>20<\/span>)<\/span>,<\/span>DATE<\/span>,<\/span>103<\/span>)<\/span>,<\/span>\r\n  COUNT<\/span>(<\/span>CASE<\/span> WHEN<\/span> DATEPART(<\/span>HOUR<\/span>,<\/span> [<\/span>DATE<\/span>]<\/span>)<\/span> BETWEEN<\/span> 9<\/span> AND<\/span> 11<\/span> THEN<\/span> 1<\/span> ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>\r\n  COUNT<\/span>(<\/span>CASE<\/span> WHEN<\/span> DATEPART(<\/span>HOUR<\/span>,<\/span> [<\/span>DATE<\/span>]<\/span>)<\/span> BETWEEN<\/span> 12<\/span> AND<\/span> 14<\/span> THEN<\/span> 1<\/span> ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>\r\n  COUNT<\/span>(<\/span>CASE<\/span> WHEN<\/span> DATEPART(<\/span>HOUR<\/span>,<\/span> [<\/span>DATE<\/span>]<\/span>)<\/span> BETWEEN<\/span> 18<\/span> AND<\/span> 20<\/span> THEN<\/span> 1<\/span> ELSE<\/span> NULL<\/span> END<\/span>)<\/span> \r\nFROM<\/span> Tickets\r\n  GROUP<\/span> BY<\/span> CONVERT<\/span>(<\/span>nvarchar(<\/span>20<\/span>)<\/span>,<\/span>DATE<\/span>,<\/span>103<\/span>)<\/span><\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
This script returns 4 columns per row so it is necessary to prepare a 4 column table. A new report has been created by choosing\u00a0Add Report<\/code>\u00a0from report selection drop down and named it as\u00a0Ticket Counts by Peak Hours<\/code>.<\/p>\n
\"\"<\/p>\n\n\n\n
\n
  [Ticket Counts:3,1,1,1]       >>> Table definition and column sizes.\r\n  >Date|9-11|12-14|18-20        >>> Header row. Starts with > char.\r\n  @TicketCountsByPeakHours      >>> SQL Script that returns rows.<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
Adding Totals to Report<\/h2>\n
\n
Use another SQL Script to display a summary footer under table.<\/p>\n\n\n\n
\n
SELECT<\/span> 'Totals'<\/span>,<\/span>\r\n  COUNT<\/span>(<\/span>CASE<\/span> WHEN<\/span> DATEPART(<\/span>HOUR<\/span>,<\/span> [<\/span>DATE<\/span>]<\/span>)<\/span> BETWEEN<\/span> 9<\/span> AND<\/span> 11<\/span> THEN<\/span> 1<\/span> ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>\r\n  COUNT<\/span>(<\/span>CASE<\/span> WHEN<\/span> DATEPART(<\/span>HOUR<\/span>,<\/span> [<\/span>DATE<\/span>]<\/span>)<\/span> BETWEEN<\/span> 12<\/span> AND<\/span> 14<\/span> THEN<\/span> 1<\/span> ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>\r\n  COUNT<\/span>(<\/span>CASE<\/span> WHEN<\/span> DATEPART(<\/span>HOUR<\/span>,<\/span> [<\/span>DATE<\/span>]<\/span>)<\/span> BETWEEN<\/span> 18<\/span> AND<\/span> 20<\/span> THEN<\/span> 1<\/span> ELSE<\/span> NULL<\/span> END<\/span>)<\/span> \r\nFROM<\/span> Tickets<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
You should create a new script and use a different handle for that script. you can access this script with\u00a0@@TicketCountsByPeakHoursTotals<\/code>.<\/p>\n
\"\"<\/p>\n
\u2026 and the report should be updated as shown here.<\/p>\n
\"\"<\/p>\n
\n
Adding\u00a0><\/code>\u00a0char in front of the row will convert it to a bold row. For this reason it has been added\u00a0><\/code>\u00a0char in front of @@TicketCountsByPeakHoursTotals to make it appear as a footer.<\/p>\n<\/div>\n
Filtering SQL Results by Date<\/h2>\n
\n
You’ll notice the example SQL script displays results for all tickets and changing dates does no change on values. However it is necessary to see the results for date ranges. To access selected date range from inside SQL Scripts you can use\u00a0{Start}<\/code>\u00a0and\u00a0{End}<\/code>\u00a0tags. Here there is another example.<\/p>\n
\"\"<\/p>\n\n\n\n
\n
SELECT<\/span>    \r\n    T.<\/span>TicketNumber,<\/span>    \r\n    MIN<\/span>(<\/span>CONVERT<\/span>(<\/span>nvarchar,<\/span>T.<\/span>Date,<\/span>105<\/span>)<\/span>)<\/span> AS<\/span> DATE<\/span>,<\/span>    \r\n    MIN<\/span>(<\/span>CONVERT<\/span>(<\/span>nvarchar,<\/span>T.<\/span>Date,<\/span>108<\/span>)<\/span>)<\/span> AS<\/span> TIME<\/span>,<\/span>    \r\n    COALESCE<\/span>(<\/span>MIN<\/span>(<\/span>CASE<\/span> WHEN<\/span> TE.<\/span>EntityTypeId =<\/span> 1<\/span> THEN<\/span> TE.<\/span>EntityName ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>'-'<\/span>)<\/span> AS<\/span> [<\/span>Customer Name]<\/span>,<\/span>    \r\n    COALESCE<\/span>(<\/span>MIN<\/span>(<\/span>CASE<\/span> WHEN<\/span> TE.<\/span>EntityTypeId =<\/span> 2<\/span> THEN<\/span> TE.<\/span>EntityName ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>'-'<\/span>)<\/span> AS<\/span> [<\/span>TABLE<\/span> Name]<\/span>,<\/span>    \r\n    MIN<\/span>(<\/span>T.<\/span>TotalAmount)<\/span> AS<\/span> TotalAmount    \r\nFROM<\/span> Tickets AS<\/span> T    \r\n    LEFT<\/span> OUTER<\/span> JOIN<\/span> TicketEntities AS<\/span> TE ON<\/span> TE.<\/span>Ticket_Id =<\/span> T.<\/span>Id    \r\nWHERE<\/span> DATE<\/span> ><\/span> '{Start}'<\/span> AND<\/span> DATE<\/span> <<\/span> '{End}'<\/span>    \r\nGROUP<\/span> BY<\/span> T.<\/span>TicketNumber    \r\nORDER<\/span> BY<\/span> DATE<\/span>,<\/span>TIME<\/span><\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
This script displays a ticket list. As date tags were included it will display tickets for only selected date range.<\/p>\n
Another report will be added by clicking\u00a0Add Report<\/code>\u00a0from report selection drop down. As this table displays 6 columns per row it is necessary to create a 6 column table.<\/p>\n\n\n\n
\n
[Tickets:1,2,2,2,2, 2]\r\n>Ticket No|Date|Time|Customer|Table|Amount\r\n@@TicketList<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
The SQL result can be accessed with\u00a0@@TicketList<\/code>\u00a0handle.<\/p>\n
\"\"<\/p>\n
Tip;<\/span>\u00a0It has been also set\u00a0Page Size<\/code>\u00a0value in centimeters for better viewing.<\/p>\n
Using Parameters in SQL Scripts<\/h2>\n\n\n\n
\n
SELECT<\/span>    \r\n    T.<\/span>TicketNumber,<\/span>    \r\n    MIN<\/span>(<\/span>CONVERT<\/span>(<\/span>nvarchar,<\/span>T.<\/span>Date,<\/span>105<\/span>)<\/span>)<\/span> AS<\/span> DATE<\/span>,<\/span>    \r\n    MIN<\/span>(<\/span>CONVERT<\/span>(<\/span>nvarchar,<\/span>T.<\/span>Date,<\/span>108<\/span>)<\/span>)<\/span> AS<\/span> TIME<\/span>,<\/span>    \r\n    COALESCE<\/span>(<\/span>MIN<\/span>(<\/span>CASE<\/span> WHEN<\/span> TE.<\/span>EntityTypeId =<\/span> 1<\/span> THEN<\/span> TE.<\/span>EntityName ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>'-'<\/span>)<\/span> AS<\/span> [<\/span>Customer Name]<\/span>,<\/span>    \r\n    COALESCE<\/span>(<\/span>MIN<\/span>(<\/span>CASE<\/span> WHEN<\/span> TE.<\/span>EntityTypeId =<\/span> 2<\/span> THEN<\/span> TE.<\/span>EntityName ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>'-'<\/span>)<\/span> AS<\/span> [<\/span>TABLE<\/span> Name]<\/span>,<\/span>    \r\n    MIN<\/span>(<\/span>T.<\/span>TotalAmount)<\/span> AS<\/span> TotalAmount    \r\nFROM<\/span> Tickets AS<\/span> T    \r\n    LEFT<\/span> OUTER<\/span> JOIN<\/span> TicketEntities AS<\/span> TE ON<\/span> TE.<\/span>Ticket_Id =<\/span> T.<\/span>Id    \r\nWHERE<\/span> DATE<\/span> ><\/span> '{Start}'<\/span> AND<\/span> DATE<\/span> <<\/span> '{End}'<\/span> AND<\/span> T.<\/span>LastModifiedUserName =<\/span> 'Administrator'<\/span>\r\nGROUP<\/span> BY<\/span> T.<\/span>TicketNumber    \r\nORDER<\/span> BY<\/span> DATE<\/span>,<\/span>TIME<\/span><\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
In this sample it has been added\u00a0and T.LastModifiedUserName = 'Administrator'\u00a0<\/code>part to the Where clause to list tickets only modified by\u00a0Administrator<\/code>\u00a0user. To display the report from multiple users you need to create a separate script for each user as it has been hardcoded user name into script.<\/p>\n
Instead of hardcoding user names into script you can configure it as a parameter.<\/p>\n\n\n\n
\n
SELECT<\/span>    \r\n    T.<\/span>TicketNumber,<\/span>    \r\n    MIN<\/span>(<\/span>CONVERT<\/span>(<\/span>nvarchar,<\/span>T.<\/span>Date,<\/span>105<\/span>)<\/span>)<\/span> AS<\/span> DATE<\/span>,<\/span>    \r\n    MIN<\/span>(<\/span>CONVERT<\/span>(<\/span>nvarchar,<\/span>T.<\/span>Date,<\/span>108<\/span>)<\/span>)<\/span> AS<\/span> TIME<\/span>,<\/span>    \r\n    COALESCE<\/span>(<\/span>MIN<\/span>(<\/span>CASE<\/span> WHEN<\/span> TE.<\/span>EntityTypeId =<\/span> 1<\/span> THEN<\/span> TE.<\/span>EntityName ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>'-'<\/span>)<\/span> AS<\/span> [<\/span>Customer Name]<\/span>,<\/span>    \r\n    COALESCE<\/span>(<\/span>MIN<\/span>(<\/span>CASE<\/span> WHEN<\/span> TE.<\/span>EntityTypeId =<\/span> 2<\/span> THEN<\/span> TE.<\/span>EntityName ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>'-'<\/span>)<\/span> AS<\/span> [<\/span>TABLE<\/span> Name]<\/span>,<\/span>    \r\n    MIN<\/span>(<\/span>T.<\/span>TotalAmount)<\/span> AS<\/span> TotalAmount    \r\nFROM<\/span> Tickets AS<\/span> T    \r\n    LEFT<\/span> OUTER<\/span> JOIN<\/span> TicketEntities AS<\/span> TE ON<\/span> TE.<\/span>Ticket_Id =<\/span> T.<\/span>Id    \r\nWHERE<\/span> DATE<\/span> ><\/span> '{Start}'<\/span> AND<\/span> DATE<\/span> <<\/span> '{End}'<\/span> AND<\/span> T.<\/span>LastModifiedUserName =<\/span> '@1'<\/span>\r\nGROUP<\/span> BY<\/span> T.<\/span>TicketNumber    \r\nORDER<\/span> BY<\/span> DATE<\/span>,<\/span>TIME<\/span><\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
It was changed\u00a0T.LastModifiedUserName = 'Administrator'\u00a0<\/code>part to\u00a0T.LastModifiedUserName = '@1'\u00a0<\/code>.\u00a0@1<\/code>\u00a0means first parameter. If you need to use more parameters you can name them as\u00a0@2<\/code>,\u00a0@3<\/code>, \u2026 etc.<\/p>\n
In this report template, it will be passed\u00a0Administrator<\/code>\u00a0value to SQL by typing parameters next to handle name.<\/p>\n\n\n\n
\n
[Tickets:1,2,2,2,2, 2]\r\n>Ticket No|Date|Time|Customer|Table|Amount\r\n@@TicketList:Administrator<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
It has been added a colon after\u00a0@@TicketList<\/code>\u00a0handle and typed user name there. It will replace with\u00a0@1<\/code>\u00a0in SQL as it is first parameter. You can also set a comma separated parameter list so you can access second parameter with\u00a0@2<\/code>and third one with\u00a0@3<\/code>. After this change the report should show only tickets created by\u00a0Administrator<\/code>.<\/p>\n
You can create multiple sections for each user. For example it is possible to change this template to include multiple user’s tickets.<\/p>\n\n\n\n
\n
[Tickets:1,2,2,2,2, 2]\r\n>Ticket No|Date|Time|Customer|Table|Amount\r\n>Administrator's Tickets\r\n@@TicketList:Administrator\r\n>Managers's Tickets\r\n@@TicketList:Manager\r\n>Waiters's Tickets\r\n@@TicketList:Waiter<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
It will create a beautiful ticket list grouped by user names.<\/p>\n
\"\"<\/p>\n
Using Parameter Sources<\/h2>\n
\n
To simplify this template you can use\u00a0Parameter Source<\/code>\u00a0feature. Instead of duplicating a report section for each user you can define a parameter list for possible values. You can change the template like this:<\/p>\n\n\n\n
\n
[Tickets:1,2,2,2,2, 2]\r\n>Ticket No|Date|Time|Customer|Table|Amount\r\n>$1's Tickets\r\n@@TicketList:$1<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
It has been replaced user name references with\u00a0$1<\/code>\u00a0keyword and deleted other sections. Now it is necessary to configure which values $1 can have. To configure a parameter list a line will be added just before first $1. That line will start\u00a0@<\/code>\u00a0char and contain a comma delimited list of possible values.<\/p>\n\n\n\n
\n
[Tickets:1,2,2,2,2, 2]\r\n>Ticket No|Date|Time|Customer|Table|Amount\r\n@Administrator,Manager,Waiter\r\n>$1's Tickets\r\n@@TicketList:$1<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
@Administrator,Manager,Waiter<\/code>\u00a0line defines values for $1 so a separate section will appear for each value inside report. That report will be same with the one that can be seen on the above screen shot.<\/p>\n
Instead of typing a parameter list you can use an SQL Script to fetch parameter values. For example if you have a single column SQL script that returns User Names you can use it instead.<\/p>\n\n\n\n
\n
[Tickets:1,2,2,2,2, 2]\r\n>Ticket No|Date|Time|Customer|Table|Amount\r\n@ @@GetUserNames\r\n>$1's Tickets\r\n@@TicketList:$1\r\n>Total|@@TicketTotal:$1<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
@@GetUserNames<\/code>\u00a0is an SQL Script that returns names from users table.<\/p>\n\n\n\n
\n
Select Name from Users<\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
\n
After this change, report will display a separate section for each user created in SambaPOS.<\/p>\n
In last template it is also included\u00a0>Total|@@TicketTotal:$1<\/code>\u00a0line to demonstrate how you can include footer totals.\u00a0@@TicketTotal<\/code>\u00a0is also an SQL script that accepts a user name parameter and returns total sum of tickets as a single value.<\/p>\n
Tip;<\/span>\u00a0You can also use parameter sources for reports you will generate by using\u00a0Custom Reporting Tags<\/a>. For advanced grouping features you can find useful information under\u00a0Custom Report Pivot Table Views<\/a>\u00a0section.<\/p>\n<\/div>\n
Creating User Specific Reports<\/h2>\n
\n
{UserId}<\/code>\u00a0and\u00a0{UserName}<\/code>\u00a0tags replaces with logged user information inside SQL scripts so you can create reports specific to logged in user.<\/p>\n\n\n\n
\n
SELECT<\/span>    \r\n    T.<\/span>TicketNumber,<\/span>    \r\n    MIN<\/span>(<\/span>CONVERT<\/span>(<\/span>nvarchar,<\/span>T.<\/span>Date,<\/span>105<\/span>)<\/span>)<\/span> AS<\/span> DATE<\/span>,<\/span>    \r\n    MIN<\/span>(<\/span>CONVERT<\/span>(<\/span>nvarchar,<\/span>T.<\/span>Date,<\/span>108<\/span>)<\/span>)<\/span> AS<\/span> TIME<\/span>,<\/span>    \r\n    COALESCE<\/span>(<\/span>MIN<\/span>(<\/span>CASE<\/span> WHEN<\/span> TE.<\/span>EntityTypeId =<\/span> 1<\/span> THEN<\/span> TE.<\/span>EntityName ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>'-'<\/span>)<\/span> AS<\/span> [<\/span>Customer Name]<\/span>,<\/span>    \r\n    COALESCE<\/span>(<\/span>MIN<\/span>(<\/span>CASE<\/span> WHEN<\/span> TE.<\/span>EntityTypeId =<\/span> 2<\/span> THEN<\/span> TE.<\/span>EntityName ELSE<\/span> NULL<\/span> END<\/span>)<\/span>,<\/span>'-'<\/span>)<\/span> AS<\/span> [<\/span>TABLE<\/span> Name]<\/span>,<\/span>    \r\n    MIN<\/span>(<\/span>T.<\/span>TotalAmount)<\/span> AS<\/span> TotalAmount    \r\nFROM<\/span> Tickets AS<\/span> T    \r\n    LEFT<\/span> OUTER<\/span> JOIN<\/span> TicketEntities AS<\/span> TE ON<\/span> TE.<\/span>Ticket_Id =<\/span> T.<\/span>Id    \r\nWHERE<\/span> DATE<\/span> ><\/span> '{Start}'<\/span> AND<\/span> DATE<\/span> <<\/span> '{End}'<\/span> AND<\/span> T.<\/span>LastModifiedUserName =<\/span> '{UserName}'<\/span>\r\nGROUP<\/span> BY<\/span> T.<\/span>TicketNumber    \r\nORDER<\/span> BY<\/span> DATE<\/span>,<\/span>TIME<\/span><\/span><\/pre>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
 <\/p>\n
This script will always return ticket list for logged in user. So each user will see \/ print their own report.<\/p>\n<\/div>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n<\/div>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n<\/div>\n
 <\/p>\n<\/div>\n<\/div>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n
 <\/p>\n
<\/code><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Adding SQL Scripts You can display result of an SQL Script in custom reports. If SQL Scripts returns a single value you can use it as a cell value. If it returns multiple values that will be formatted as a table row. In other words SQL result will be converted to a list where each […]<\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[],"class_list":["post-13937","post","type-post","status-publish","format-standard","hentry","category-reports"],"_links":{"self":[{"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/posts\/13937","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/comments?post=13937"}],"version-history":[{"count":9,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/posts\/13937\/revisions"}],"predecessor-version":[{"id":14977,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/posts\/13937\/revisions\/14977"}],"wp:attachment":[{"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/media?parent=13937"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/categories?post=13937"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/tags?post=13937"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}