Implementing Row-Level Inventory Overrides in PharmaStock

 I focused on improving how inventory data is edited in PharmaStock by implementing row-level override functionality.

Previously, updating medication details such as generic name or strength would affect all inventory records tied to that medication. To solve this, I introduced override fields directly on the InventoryStock entity. This allows each inventory row to store its own version of medication data without modifying the shared medication record.

On the backend, I created dedicated PATCH endpoints for each override field, including generic name, medication name, NDC, strength, and dosage form. These endpoints update only the targeted inventory record. I also updated the mapping layer to prioritize override values when present, falling back to the base medication data when they are not.

On the frontend, I refactored the Angular save logic to detect which fields were changed and dynamically call the appropriate PATCH endpoints. The save operations are executed sequentially to ensure data consistency, and the UI refreshes automatically after completion.

This implementation aligns the system with real-world inventory workflows, where the same medication can exist in multiple contexts with slight variations. It also improves data safety by preventing unintended global updates. 



Comments

Post a Comment

Popular posts from this blog

PharmaStock: Backend Infrastructure & Database Connectivity

 This week marked the transition from planning and design into real backend development. After organizing the project structure and defining use cases in previous weeks, I focused on building the technical foundation that the rest of the application will depend on. The primary goal was completing SCRUM-16, which involved connecting the ASP.NET Core backend API to a MySQL database and verifying that the system could successfully generate and manage database tables. I began by configuring MySQL to run inside a Docker container. Using Docker ensures that every developer on the team works against the same database environment, which reduces setup inconsistencies and avoids the common “it works on my machine” problem. Once the container was running correctly, I verified that it could be started, stopped, and inspected reliably. Next, I integrated Entity Framework Core with the Pomelo MySQL provider and registered the DbContext within the application. This step allows the backend to m...
Read more

PharmaStock Backend Progress Complete all backend endpoints

Image
 I completed the full Medication API (GET, POST, PUT, PATCH, DELETE) and finished SCRUM-37, implementing the stock quantity adjustment endpoint. Inventory quantities can now be increased or decreased, negative values are prevented, and all changes persist correctly in the database. I also finalized the inventory creation flow with duplicate lot validation and verified everything through Swagger testing. On the frontend side, I started SCRUM-38 and began building the Angular inventory list component to connect the UI to the new backend functionality. Overall, this week solidified the backend foundation and began transitioning into full-stack development. Medication Post Workflow            Medication Post          Post Inventory for new medication               Inventory adjustments
Read more

PharmaStock: Sprint Planning Complete

This week was focused on finalizing project planning and getting everything ready for development. I completed the setup of the Jira board , finalized all sprints for the full length of the project, and added clear completion criteria for each sprint and task. This gives the team a clear roadmap from MVP through enhancement features. I also synced my local GitHub setup with the main project repository and verified that the branching structure is ready for feature development. With planning complete and source control aligned, the project is now fully prepared to move into active development next week.
Read more