Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →This installment extends a read-only product grid with create and delete actions. Lattice Grid collects product details and sends them to a Node.js function through an AWS Lambda Function URL; the function performs the DynamoDB writes. The example is Tony Goodchild’s tutorial implementation, which requires Lattice Grid 1.76.0 or later—not an independently tested deployment.
What Part 2 adds
The example builds on Part 1’s product-list application. Part 1 created the DynamoDB table, Lambda function, and read-only page; Part 2 adds products using the grid’s row form and deletes them from a row context menu. The tutorial’s code is in the part-2 folder of the tutorial repository.
As an Amazon Associate I earn from qualifying purchases.
The browser does not write directly to DynamoDB. It sends HTTP requests to a Lambda Function URL, and the Node.js function carries out the database operations. That separation keeps database access in the server-side function, although the sample endpoint itself has no authentication.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →How adding a product works
- Collect the fields. The grid’s built-in row form gathers product details and invokes its
createhook. - Send the request. The page posts the form data as JSON to the Lambda Function URL.
- Validate and store. The function assigns a SKU if one was not supplied, stamps an
updateddate, and writes the product to DynamoDB. A condition prevents an existing SKU from being silently overwritten. - Update the grid. The function returns the stored product, which the grid adds as a row.
The duplicate-SKU condition matters because it makes a conflicting create fail rather than quietly replacing an existing item. The server’s response also lets the grid display the saved record, including server-assigned values.
#1 Best Overall
How deleting a product works
- Choose the row action. A context-menu action on a product row initiates deletion.
- Confirm. The grid asks the user to confirm before proceeding.
- Identify the item. The page sends a DELETE request containing the row’s SKU.
- Remove it after success. The grid discards the row only after the server reports that the delete operation succeeded. If the request fails, the row remains visible instead of disappearing from the interface while still stored in DynamoDB.
Configure the Lambda Function URL for browser requests
The tutorial says the Function URL initially allows only GET. Because the page also sends JSON POST and DELETE requests, update its CORS configuration to permit those methods and the content-type header. Otherwise, the browser can block the cross-origin request even if the function code and database permissions are correct.
Give the Lambda role the required DynamoDB access
Part 1 uses the AWS-managed AmazonDynamoDBReadOnlyAccess policy, which is not enough for create and delete. The tutorial replaces it with a table-scoped inline policy for the Products table. It lists scan, get, put, update, and delete permissions; update is included for the following installment. Scope permissions to the table the function needs rather than granting broad DynamoDB access.
Rank #2
For JavaScript projects, AWS’s DynamoDB guide for SDK v3 documents both the low-level client and the higher-level document client, and recommends using the latest SDK. Its examples show document-client put and delete operations. This is current AWS guidance for the SDK, not a verification of the tutorial repository’s dependency versions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Security and scale limits to address before production
The sample URL is unauthenticated
The tutorial warns that anyone who has the Function URL can change products. CORS is a browser access control, not an authentication mechanism: it does not establish who is authorized to create or delete records. A production adaptation needs an authentication and authorization design appropriate to its users and data.
The page loads the full product list
The example returns every product on each load. The tutorial identifies server-side filtering, sorting, or paging as next steps for larger datasets. Those capabilities reduce the amount of data the endpoint must return and let clients request only the records they need.
Keep the create safeguard server-side
The duplicate-SKU condition is enforced by the DynamoDB write, rather than relying only on the grid to check for collisions. This is important because a client-side check alone cannot prevent another request from creating the same SKU between the check and the write.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
