Open MSupply V2.12 Demographics Issue: Current Population Value Not Saving

Hey guys! Today, we're diving into a peculiar issue reported in Open mSupply version 2.12 concerning the Demographics section. Specifically, users are encountering a problem where the 'Current population' value isn't being saved as expected. Let's break down the problem, explore the expected behavior, provide a step-by-step guide to reproduce the issue, and discuss the environment in which this bug manifests. Buckle up; we're about to get technical but in a super chill way!

What Went Wrong? 😲

So, here’s the scoop. Imagine you're working with Open mSupply, specifically version 2.12, and you're in the Demographics section. You go ahead and enter a value for the 'Current population,' feeling all productive and stuff. You click 'Save,' and you even get that reassuring 'Successfully saved' message. Sweet, right? Wrong! You refresh the page, expecting your diligently entered value to be there, but poof, it's gone! It's like the system is playing a prank on you. This can be incredibly frustrating, especially when you're trying to keep accurate records.

To give you a clearer picture, someone actually shared a screenshot highlighting this exact issue. Visual aids are always a plus, right? It helps to see that you're not alone in this digital wilderness. Understanding the issue is the first step, and clearly, this one involves a disappearing act of crucial data. Let’s dig deeper into why this might be happening.

Data persistence is a critical aspect of any software application, especially in systems like Open mSupply where accuracy and reliability are paramount. The fact that the 'Successfully saved' message appears, yet the data doesn't persist, suggests a potential disconnect between the user interface feedback and the underlying data storage mechanism. This discrepancy can stem from various factors, such as caching issues, database transaction failures, or even a simple oversight in the code logic. To ensure the integrity of the system, it’s crucial to pinpoint the exact cause and implement a robust solution. After all, we want our data to stick around, not vanish into thin air!

Expected Behaviour 🤔

Okay, so what should happen? Simple! When you enter a value for 'Current population' and hit 'Save,' that value should, you know, stay saved. Refreshing the page shouldn't make it vanish like a magician's rabbit. It should persist, stick around, be there when you need it. That’s the expected behavior – the system doing what it's supposed to do.

Imagine the frustration of constantly re-entering data, especially in a system designed to streamline processes. The expectation of data persistence is fundamental to user trust and system usability. If a user can't rely on the system to save their inputs, it erodes confidence and increases the likelihood of errors. Therefore, addressing this issue isn't just about fixing a bug; it's about upholding the core principles of reliable data management.

Think of it like writing in a notebook. You write something down, close the notebook, and when you open it again, you expect your writing to still be there. The same principle applies to digital systems. Data should be durable, meaning it remains intact even after system restarts, page refreshes, or other interruptions. This expectation is especially critical in sectors like healthcare and supply chain management, where accurate and consistent data is essential for informed decision-making.

How to Reproduce 🔨

Alright, let's get our hands dirty and try to recreate this bug. Here’s a step-by-step guide to reproduce the disappearing 'Current population' value:

1. Go to Manage -> Demographics on the Central Server: Fire up your Open mSupply, navigate to the 'Manage' section, and then click on 'Demographics'. This is where the magic (or rather, the bug) happens.
2. Make sure you are starting from scratch and have no existing demographics setup: To ensure a clean test, start with a blank slate. No pre-existing data to mess with our results.
3. In General Population, enter the value (don't add any other demographics): This is key! Enter a value in the 'General Population' field, but don't add any other demographic info. This seems to be the specific scenario that triggers the bug.
4. Hit Save -> refresh -> the value is not there anymore: Click that 'Save' button with anticipation, then refresh the page. Watch in mild horror as your value disappears into the digital ether.
5. I cannot recreate the issue when other demographics are entered, so I think this is only happening when we enter General Population only: This is a crucial observation! The bug seems to be isolated to the case where only 'General Population' is entered. If you add other demographic data, the issue doesn't pop up. This gives us a valuable clue about the root cause.

Reproducing a bug is half the battle in fixing it. By providing these clear, concise steps, we make it easier for developers to pinpoint the problem and squash it. The more detailed the steps, the better the chances of consistently recreating the issue, which is essential for effective debugging. It's like being a detective, following the clues to solve the mystery of the disappearing data!

The fact that the issue only occurs when 'General Population' is entered without any other demographic data suggests that there might be a conditional logic error in the code. Perhaps there's a validation check or a data persistence routine that is only triggered when multiple demographic fields are populated. Identifying these specific conditions is crucial for developers to target their efforts and implement the correct fix.

Your Environment 🌱

Knowing the environment where the bug occurs is crucial for troubleshooting. Think of it as the crime scene – we need to gather all the evidence! Here’s the environmental setup where this issue was observed:

• Open mSupply Version: V2.12.00-develop-09241424 – This is the specific version of Open mSupply where the bug was found. Knowing the version number helps developers focus on the relevant codebase.
• Legacy mSupply Central Server Version: V8.04.09 – The version of the central server is also important, as it might interact with the demographics data.
• Platform: Google Chrome (browser for Mac) – The browser and operating system can sometimes influence how software behaves. In this case, it's Google Chrome on a Mac.
• Database type: PostgreSQL – The type of database used can also be a factor. Here, it's PostgreSQL.

This information helps narrow down the possible causes. For instance, a bug might be specific to a particular browser version or database configuration. Providing these details saves developers time and effort in replicating the issue and finding a solution. It's like giving them a detailed map to the bug's hiding place.

Understanding the environment is not just about listing the software and hardware specifications; it’s about recognizing the potential interactions and dependencies that might contribute to the bug. For example, certain JavaScript behaviors might differ slightly between browsers, or specific PostgreSQL configurations might impact data persistence. By meticulously documenting the environment, we empower developers to make informed decisions and address the root cause of the problem more effectively.

Conclusion

So, there you have it! A detailed look at the disappearing 'Current population' value in Open mSupply v2.12. We've covered what went wrong, the expected behavior, how to reproduce the bug, and the environment in which it occurs. By understanding these aspects, we're one step closer to squashing this bug and making Open mSupply even more awesome. Stay tuned for updates, and happy data saving (hopefully!).

This comprehensive analysis not only highlights the specific issue but also underscores the importance of clear communication, detailed documentation, and collaborative problem-solving in software development. By working together and providing as much information as possible, we can ensure that these quirks are resolved efficiently, leading to a more robust and user-friendly system for everyone.

And that's a wrap, folks! Remember, every bug fixed is a step towards a better software experience. Keep reporting those issues, and let's make Open mSupply the best it can be!