Routing
detail_dataset_urusan
Matched route
Route Parameters
| Name | Value |
|---|---|
| id | "40" |
Route Matching Logs
Path to match:
/dataset/detail_urusan/40
| # | Route name | Path | Log |
|---|---|---|---|
| 1 | _preview_error | /_error/{code}.{_format} | Path does not match |
| 2 | _wdt | /_wdt/{token} | Path does not match |
| 3 | _profiler_home | /_profiler/ | Path does not match |
| 4 | _profiler_search | /_profiler/search | Path does not match |
| 5 | _profiler_search_bar | /_profiler/search_bar | Path does not match |
| 6 | _profiler_phpinfo | /_profiler/phpinfo | Path does not match |
| 7 | _profiler_search_results | /_profiler/{token}/search/results | Path does not match |
| 8 | _profiler_open_file | /_profiler/open | Path does not match |
| 9 | _profiler | /_profiler/{token} | Path does not match |
| 10 | _profiler_router | /_profiler/{token}/router | Path does not match |
| 11 | _profiler_exception | /_profiler/{token}/exception | Path does not match |
| 12 | _profiler_exception_css | /_profiler/{token}/exception.css | Path does not match |
| 13 | api | /api/{id} | Path does not match |
| 14 | api_get | /api/{id}/get/{row} | Path does not match |
| 15 | api_get_data | /get/api | Path does not match |
| 16 | api_json | /data.json | Path does not match |
| 17 | dataset | /dataset | Path does not match |
| 18 | dataset_detail | /dataset/{id}/detail | Path does not match |
| 19 | dataset_form | /dataset/request/{id} | Path does not match |
| 20 | dataset_dataset_table | /dataset/{id}/dataset_table | Path does not match |
| 21 | dataset_excel | /dataset/{id}/{tipe}/download_excel | Path does not match |
| 22 | dataset_excel_kmj | /dataset/{id}/{tipe}/download_excel_kmj | Path does not match |
| 23 | dataset_chart_json | /dataset/{id}/chartJson | Path does not match |
| 24 | dataset_dcat | /dataset/{id}/dcat | Path does not match |
| 25 | dataset_urusan | /dataset/urusan/{id} | Path does not match |
| 26 | detail_dataset_urusan | /dataset/detail_urusan/{id} | Route matches! |
Note: These matching logs are based on the current router configuration, which might differ from the configuration used when profiling this request.