September 22, 2026

myLIMSweb | Version 4.7.676

This release makes your records more complete and your daily work smoother, with two improvements and two fixes in myLIMS. Field collections now keep every data point when they change hands, administrators decide when Portal users can remove analyses, reanalyzed samples keep their reference methodology, and columns on the Perform Analyses screen stay the size you set. Below is what changed and what you will notice in practice.

🚀 Improvement

Field collections keep every data point when another collector takes over

What was happening?

When a field collection was started by one collector and continued by another through partial synchronizations from myLIMS mobile, myLIMS needed to hold on to what was already sent, recognize photos and signatures it had already received, and show clearly who did what along the way.

Why was this a problem?

Without that, a collection that changed hands could leave gaps, repeat attachments, or make it hard to reconstruct the history of a sample when someone asks later.

What changed?

myLIMS now keeps the collection reserved for the field team after each partial synchronization, so the next collector can continue it. Data, analyses, and raw data history are applied every time the app synchronizes, and photos and signatures that were already received are not stored twice. The sample and activity history now records each successful synchronization and each change of the responsible user.

What will you notice in practice?

A collection can pass from one collector to another and arrive in myLIMS complete, with a clear history of who collected what and when.

Before vs. Now

Before: A collection continued by another collector depended on the final synchronization, and the history of partial steps was limited.

Now: Every synchronization is applied and recorded, attachments are not duplicated, and changes of responsible user appear in the history.

#132662

🚀 Improvement

Decide when Portal users can remove analyses from their sample requests

What was happening?

Removing analyses from a sample request in the Portal is a flexibility some labs want to offer and others do not, and there was no setting in myLIMS to choose.

Why was this a problem?

Without a clear switch, a lab could not decide which behavior its Portal users should see, or be sure the sample and its value match the analyses that remain.

What changed?

Administrators now have an option in myLIMS Web, in the Portal settings on the Commercial Proposal tab, to allow or block analysis removal on sample requests. It is off by default, so nothing changes until you turn it on, and it works together with your existing sample request and commercial proposal settings. When a request arrives with analyses removed, myLIMS creates the sample with only the remaining analyses and recalculates the value, keeping your negotiated discounts.

What will you notice in practice?

You choose when to offer this flexibility, and each sample and its value reflect exactly what your customer kept on the request.

Before vs. Now

Before: There was no myLIMS setting to control whether Portal users could remove analyses from a request.

Now: You turn analysis removal on or off in the Portal settings, and the sample and its value follow the analyses that remain.

#133895

🔧 Fix

Reanalyzed samples now keep the reference methodology of their method

What was happening?

When you clicked Reanalyze on a validation sample, the analyses were recreated from the method, but the reference methodology was left blank on the sample, even when it was filled in on the method and in the calculation spreadsheet.

Why was this a problem?

The sample record was missing information you had configured, and reanalyzing again did not bring it back, so you had to work around it.

What changed?

Reanalyze now copies the reference methodology from the method together with the rest of the method data, so the sample reflects the current method configuration.

What will you notice in practice?

After you reanalyze a sample, the reference methodology appears on it just as it is set on the method.

Before vs. Now

Before: Reanalyze recreated the analyses but left the reference methodology blank on the sample.

Now: Reanalyze brings the reference methodology from the method onto the sample.

#133898

🔧 Fix

Resizing a column on the Perform Analyses screen now changes only that column

What was happening?

On the Perform Analyses screen, when you dragged the edge of a column in the Analyses or Information tab, the other columns resized on their own. The same happened in the window you use to advance several analyses to their next stage.

Why was this a problem?

The view became distorted and you had to adjust several columns again just to read your results comfortably.

What changed?

Each column in those grids now keeps its own width. Only the column you resize changes, and the grid scrolls sideways when it needs more room.

What will you notice in practice?

You set the columns the way you like once, and they stay that way while you enter and review results.

Before vs. Now

Before: Resizing one column made the other columns resize automatically.

Now: Only the column you resize changes, and the rest stay as they were.

#132720

September 15, 2026

myLIMSweb | Version 4.7.673 · Portal Web | Release 1287 · myLIMS mobile | Version 1.2.53

This release lets you shape sample requests exactly as you need them, keeps your analysis results consistent across web and mobile, and makes field collection continuous, with two improvements and one fix across the Portal, myLIMS, and myLIMS mobile. Below is what changed and what you will notice in practice.

🚀 Improvement

You can now remove analyses from a sample request in the Portal

What was happening?

In the Portal, once you added analyses to a sample request, you could not take one back out before completing the sample copy, so an analysis you no longer wanted stayed on the request.

Why was this a problem?

Keeping an analysis you did not want on the request means extra cleanup later and a request that does not match what you actually need, and it can affect what is charged.

What changed?

You can now remove analyses from a sample request before you finish copying the sample, when your Portal is configured to allow it. If an analysis has a linked prerequisite, the Portal unchecks them together and asks you to confirm, and it will not let you remove a main analysis without its prerequisite. The request value is recalculated automatically so only the analyses you keep are counted, and your negotiated discounts are preserved. Subsamples work the same way.

What will you notice in practice?

You can shape each sample request to exactly the analyses you need, with the price updating to match, before you send it.

Before vs. Now

Before: Analyses added to a sample request could not be removed before completing the copy.

Now: You can remove analyses before completing the copy, with prerequisites handled for you and the price recalculated automatically.

#133895

🔧 Fix

Attributes now clear correctly when an analysis advances to its next stage

What was happening?

When an analysis moved to its second stage and an attribute had been filled in, a spreadsheet rule set to clear that attribute did not take effect if the analysis was done through Mobile Analysis. In myLIMS Web it already worked correctly.

Why was this a problem?

An attribute that stays filled in against your configured rule leaves the result inconsistent depending on where the work was done, which you then have to notice and correct by hand.

What changed?

The attribute is now cleared exactly as your spreadsheet rule defines when an analysis advances to its second stage, including when the work is done through Mobile Analysis, so web and mobile behave the same way.

What will you notice in practice?

Your analysis results follow the same rules whether the work is done on the web or on Mobile Analysis, so you can trust the record without checking it twice.

Before vs. Now

Before: The attribute could stay filled in on a second stage when the analysis was done through Mobile Analysis.

Now: The attribute clears according to your rule on both web and Mobile Analysis.

#132381

🚀 Improvement

You can save and send a partial collection from the field

What was happening?

If you could not finish a collection in one pass in the field, there was no way to keep the information you had already entered, so continuing the activity later or handing it to another collector could lose what you captured.

Why was this a problem?

Losing entries you already made means repeating work in the field and risking gaps in the collection record.

What changed?

You can now register and send a partial collection to myLIMS without finalizing it, so the information you entered is saved and another collector can continue the same activity without losing anything already captured.

What will you notice in practice?

You can start a collection, save and send what you have, and pick it up later or hand it off, and every entry is preserved.

Before vs. Now

Before: An unfinished collection could lose the data already entered if it was continued later or by someone else.

Now: You can save and send a partial collection, and what you captured is kept for whoever continues it.

#132663

September 8, 2026

myLIMSweb | Version 4.7.671 · Portal Web | Version 4.16.0 · DataViewer | Version 1.13 · myLIMS mobile | Version 1.1.0

This release keeps your data honest, your dashboards open, and your field collection reliable, with three fixes and one improvement across the Portal, DataViewer, myLIMS, and myLIMS mobile. Below is what changed and what you will notice in practice.

🔧 Fix

Your download messages now match what actually happened

What was happening?

On the Portal Reports screen, when you downloaded files by type, you saw a message saying your files had downloaded successfully even in cases where the files did not actually reach you.

Why was this a problem?

A success message that appears when nothing was delivered leaves you unsure whether you really have your files, and you might move on believing a report is in hand when it is not.

What changed?

The Portal now shows the success message only once your files are confirmed as delivered. When a download does not complete, it shows a clear failure message, translated into your Portal language, so you know to try again.

What will you notice in practice?

Every download now tells you exactly what happened: a success message when your files arrive, and a clear failure message when they do not.

Before vs. Now

Before: The Portal showed a success message even when the files were not delivered.

Now: The Portal confirms success only when your files arrive, and warns you clearly when a download fails.

#133400

🔧 Fix

Your dashboards stay accessible after a profile change

What was happening?

When your user profile was changed, you could suddenly get an error trying to open a dashboard, even though your profile still had access to it.

Why was this a problem?

Losing access to a dashboard you are entitled to see interrupts your work and blocks decisions that depend on that data, with no clear reason why.

What changed?

DataViewer now handles report permissions that include a workspace with no report list gracefully: it skips that workspace and keeps checking the rest, instead of stopping with an error.

What will you notice in practice?

Your dashboards open reliably after a profile change, as long as your profile grants access, so you keep uninterrupted access to your data.

Before vs. Now

Before: A profile change could trigger an error that blocked access to dashboards you were entitled to see.

Now: Dashboards open reliably after a profile change, with access still governed by your permissions.

#132893

🚀 Improvement

Automatic document generation is faster

What was happening?

When myLIMS generated documents automatically, one of the underlying checks ran a heavy query that took longer than it should and used more resources than necessary.

Why was this a problem?

A slow step in document generation adds waiting time and puts extra load on the system, which you feel most when documents are produced in volume.

What changed?

The check that confirms whether a file is already stored now uses a lightweight lookup instead of pulling the full record, so it completes quickly.

What will you notice in practice?

Automatic document generation runs faster and lighter, so your results and documents are ready with less waiting.

Before vs. Now

Before: A heavy query slowed automatic document generation and consumed extra resources.

Now: A lightweight check keeps automatic document generation fast and efficient.

#127039

🔧 Fix

Field collection on myLIMS mobile is more reliable

What was happening?

In the Collection module on myLIMS mobile, yes or no fields did not respond when you tapped them, photos and signatures you removed before syncing could still be sent, the Date and Time field could show an invalid value after syncing, and the screen sometimes jumped or scrolled back to the top while you were filling it in.

Why was this a problem?

When the collection screen does not behave as expected in the field, capturing a sample takes longer and you cannot fully trust that what you recorded is what syncs back to the lab.

What changed?

Yes or no fields now work as a simple two state checkbox that responds to your tap, only the attachments you actually kept are synced, the Date and Time field syncs correctly, and the screen stays where you are while you fill it in. Leaving the Analysis module through normal navigation now frees its license as expected, and the login screen shows the updated company logo.

What will you notice in practice?

Collecting a sample in the field is smoother and what you capture syncs back to the lab faithfully, so you can rely on the record.

Before vs. Now

Before: Checkboxes did not respond, removed attachments could still sync, dates could show an invalid value, and the screen jumped while you worked.

Now: Checkboxes respond to your tap, only kept attachments sync, dates sync correctly, and the screen stays steady while you collect.

#129077

September 1, 2026

myLIMSweb | Version 4.7.666 · Portal Web | Version 4.15.0

This release keeps your sample results clean and your Portal secure, with one fix and one improvement. Below is what changed and what you will notice in practice.

🔧 Fix

Raw data no longer stays stuck when you remove an analysis

What was happening?

When you removed an analysis from a sample, its raw data did not always go away with it. It stayed on the sample whenever that raw data drew its value from two or more analyses.

Why was this a problem?

Raw data left behind does not belong to the sample any more, so the sample looked cluttered and the leftover values could be confusing when you reviewed or reported results.

What changed?

myLIMS now checks all of the analyses a raw data value is linked to and keeps it only when at least one of them is still on the sample. This works for any number of linked analyses.

What will you notice in practice?

When you remove an analysis, its raw data is cleared right away, just like raw data that was linked to a single analysis, so the sample shows only what belongs on it.

Before vs. Now

Before: Raw data linked to two or more analyses stayed stuck on the sample after you removed the analyses.

Now: Raw data is cleared as soon as no linked analysis remains on the sample.

#132384

🚀 Improvement

Password recovery on the Portal is protected against a flood of reset emails

What was happening?

On the Portal, the password recovery screen showed only a generic error when a request could not be completed, and repeated requests were not limited, so the recovery flow could be used to send a burst of reset emails.

Why was this a problem?

A generic error left you unsure what went wrong, and a flow that can be triggered repeatedly can fill an inbox with reset emails you did not ask for.

What changed?

The Portal now limits how many recovery requests can be made in a short time and shows a clear, translated message when that limit is reached. The button also stays disabled while a request is processing, so a second click does not send another request.

What will you notice in practice?

If you request a password reset several times in quick succession, the Portal now tells you clearly to try again later instead of showing a generic error, and you and your contacts are protected from a flood of reset emails.

Before vs. Now

Before: The recovery screen showed a generic error, and repeated requests were not limited.

Now: Recovery requests are limited and a clear message explains when to try again.

#132796

August 25, 2026

myLIMSweb | Portal Web Version 4.14.0

This release gives the Portal a refreshed, on brand look, and includes two useful fixes. Below is what changed and what you will notice in practice.

🚀 Improvement

The Portal now wears the Confience colors

What was happening?

The Portal used an older color set that did not fully match the Confience brand, and the colors were applied unevenly across screens, so the look drifted from one page to the next.

Why was this a problem?

A Portal that does not match the Confience identity feels less polished to the customers and partners who use it, and inconsistent colors across screens make the experience harder to trust at a glance.

What changed?

The Portal now uses the official Confience color palette across buttons, text, icons, tables, and charts, applied consistently on every screen, including login, password recovery, document validation, the panel, reports, charts, and commercial proposals. Contrast and readability were preserved.

What will you notice in practice?

When you open the Portal, it looks cleaner and consistently on brand, with the same Confience colors everywhere you go.

Before vs. Now

Before: The Portal showed an older, uneven color set that did not fully match the Confience brand.

Now: The Portal uses the official Confience color palette consistently across every screen.

#132560

August 18, 2026

myLIMSweb | Version 4.7.662

This release brings your AI assistant fully under the Fluence name, gives you more control over it, and restores a helpful edit history detail. Below is what changed and what you will notice in practice.

🚀 Improvement

Your AI assistant is now Fluence

What was happening?

The AI assistant inside myLIMS Web still appeared under its old name, in the interface, which did not match the name you see elsewhere for the same assistant.

Why was this a problem?

Seeing two different names for the same assistant is confusing and makes it harder to know where to turn for help inside myLIMS.

What changed?

Every place that used to show the old name now shows Fluence, across the supported languages. The way the assistant works is unchanged.

What will you notice in practice?

You see one consistent name, Fluence, for the AI assistant throughout myLIMS Web.

Before vs. Now

Before: The assistant appeared as the old name in the interface.

Now: The assistant appears as Fluence everywhere in myLIMS Web.

#125898

🚀 Improvement

Minimize Fluence and see it correctly across your environments

What was happening?

The floating Fluence button sat on top of the items per page control, it appeared for some users who sign in through the legacy login and should not have access to it, and moving from one environment to another could show a cookie related error instead of Fluence.

Why was this a problem?

The button could get in the way of the controls beneath it, the wrong users saw it, and switching environments did not reliably show the assistant, which made Fluence feel inconsistent.

What changed?

You can now minimize Fluence, and it remembers your choice. It is hidden for users on the legacy login, and it displays correctly for whichever environment you are working in.

What will you notice in practice?

Fluence stays out of the way when you minimize it, appears only where it should, and follows you cleanly as you move between environments.

Before vs. Now

Before: The Fluence button could cover the items per page control, showed for some legacy login users, and could error when you changed environments.

Now: You can minimize Fluence, it is hidden for legacy login users, and it displays correctly across environments.

#131343

🔧 Fix

See who last edited an Analysis Group, and when

What was happening?

On the Analysis Group screen, the notice showing who last edited or activated the record appeared only right after you saved, then disappeared when you opened the record again.

Why was this a problem?

Without that notice you could not easily confirm who last changed an Analysis Group and when, which matters for review and audit.

What changed?

The record now loads the last edit details every time you open it, so the notice showing who edited the record and when is there whenever you view it.

What will you notice in practice?

When you open an Analysis Group, you can see who last edited or activated it and when, not only right after saving.

Before vs. Now

Before: The last edit and activation notice showed only just after saving and then vanished when you reopened the record.

Now: The notice shows who last edited or activated the Analysis Group, and when, every time you open it.

#128540

🚀 New

Fluence AI is starting to roll out

Fluence AI is beginning to roll out across myLIMS, starting today and reaching every lab by August 28. It is the assistant inside myLIMS that answers your questions about the platform from the myLIMS knowledge base, and shows its source every time.

What is Fluence AI?

Fluence AI answers your questions about how myLIMS works, in plain language, drawn from the myLIMS knowledge base. Every response arrives with its source attached, so you can open the article behind any answer and confirm it for yourself.

Why it matters

Fluence AI is built to Eliminate manual and tedious work so your lab operates with the speed and precision you require. Instead of searching help articles or waiting on a support reply to learn how a feature works, you ask Fluence and get a clear, sourced answer right inside myLIMS.

And because every answer names the article it came from, you always know where the guidance originated, which supports the traceability that runs through the whole platform: Gain complete traceability with access to trustworthy data to always be ready for audits, decisions, and expansion.

What you will be able to do

·       Ask Fluence how to do something in myLIMS in your own words.

·       Get answers drawn from the myLIMS knowledge base, in plain language.

·       See the source behind every answer, so you can open the article and confirm it.

·       Rely on honest answers: when Fluence cannot find something in the knowledge base, it tells you plainly instead of guessing.

What to expect during the rollout

·       Fluence is arriving in stages between August 5 and August 28.

·       If you do not see it yet, it is on the way. There is nothing you need to do to turn it on.

·       Every myLIMS user will have access by August 28, and we will confirm here when the rollout is complete.

Fluence is part of the same promise behind myLIMS: A platform that evolves with you—guided by teams who understand your science.

myLIMSweb | Version 4.7.654

This release brings a set of fixes to your daily work across myLIMS Web and myLIMS mobile. Below is what changed and what you will notice in practice.

🔧 Fix

Create Sample by Collection Point again shows only the points linked to your profiles

What was happening?

When you created samples through Samples, Create By Collection Point, the screen listed every collection point registered in the system instead of only the ones linked to your profiles. If you picked a point outside your permissions, creation still would not go through, but the full list was there to scroll past.

Why was this a problem?

A list with points you cannot use makes it slower to find the right one and easier to pick the wrong point by mistake. You expect the screen to show only the points you are allowed to work with, so a longer list adds doubt to a routine step.

What changed?

The screen again shows only the collection points linked to your profiles. The same correct list now applies across the screens that use collection points, and your existing translations are kept.

What will you notice in practice?

When you create samples by collection point, you see a shorter list that matches your access, so you find the right point quickly and create samples with confidence.

Before vs. Now

Before: The screen listed every collection point in the system, including points outside your permissions, so you scrolled past points you could not use.

Now: The screen shows only the points linked to your profiles, so the list matches your access.

#126893

🔧 Fix

Adding analyses by analysis group to a specification works again

What was happening?

When you added analyses to a specification by analysis group, the action did not complete and the analyses were not added. If you had removed the analyses from a specification and tried to add them back by group, you were left unable to restore them.

Why was this a problem?

Building and maintaining a specification is central to your setup, and not being able to add analyses by group forced you to look for a workaround or stop the task, which slowed work that should be straightforward.

What changed?

Adding analyses to a specification by analysis group now completes as expected. The information the action needs is loaded correctly, so the analyses are added the first time.

What will you notice in practice?

You can add analyses to a specification by analysis group again, and build and maintain your specifications without a workaround.

Before vs. Now

Before: Adding analyses by analysis group did not complete, so the analyses were not added to the specification.

Now: Adding analyses by analysis group completes, and the analyses are added as expected.

#127332

🔧 Fix

Sample collections no longer get stuck on the device during sync

What was happening?

While collecting on myLIMS mobile, if a free text field held more characters than the system accepts, the collection did not sync back to myLIMS Web and gave no clear reason. Part of a collection could sync while the rest stayed on the device.

Why was this a problem?

Samples that stay on the device hold up the collection process and put your data at risk, and because there was no message at the moment of entry, it was hard to tell why the sync did not complete.

What changed?

myLIMS mobile now checks the length of these fields as you enter text. If the text is too long, you see a warning and cannot save over the limit, so the collection stays within what the system accepts and syncs back cleanly.

What will you notice in practice?

You are told right away when a text entry is too long, so your collections sync back reliably and no samples are left behind on the device.

Before vs. Now

Before: A text entry over the limit could make a collection fail to sync with no warning, leaving samples stuck on the device.

Now: You get a warning as you type when an entry is too long, so collections stay within the limit and sync back reliably.

#128560

July 21, 2026

myLIMSweb | Version 4.7.651

This release brings a set of fixes and improvements to your daily work in myLIMS Web. Below is what changed and what you will notice in practice.

🔧 Fix

Scheduled sample and activity generation no longer creates duplicates

What was happening?

You set up samples and activities to be generated automatically in advance through the scheduler, and once in a while the same sample or activity was created more than once. Each duplicate came in with its own new ID, so at first glance the records looked normal, even though the schedule was set to create them only once.

Why was this a problem?

Duplicate samples and activities meant extra records to find, review, and remove by hand, and they put the accuracy of your data at risk. Because the duplicates appeared only occasionally, you could not always predict when a clean up would be needed, which added uncertainty to work that should simply run on its own.

What changed?

Scheduled generation now protects against creating the same sample or activity twice, even when several generations are triggered close together. Before a record is created, the system checks again against a fresh reading to confirm it does not already exist.

What will you notice in practice?

Samples and activities scheduled for automatic advance generation are created exactly once, following the settings you configured. There are no duplicate records to track down and remove.

Before vs. Now

Before: Scheduled advance generation could occasionally create the same sample or activity more than once, each with its own ID. You had to find and remove the duplicates by hand.

Now: Scheduled advance generation creates each sample and activity only once. Your records stay clean, with no manual clean up.

#123574

🔧 Fix

The Production Date column filter now returns the exact day and works with other filters

What was happening?

On the Samples screen, you filtered by the custom "Production Date" column and the results did not match the day you selected. The filter could bring records from the following day and skip records recorded exactly at midnight. When you combined "Production Date" with a second filter, the second one was often ignored, and the status tabs, such as Not Received, Received, Not Finalized, Finalized, and Published, could return the previous day.

Why was this a problem?

You could not trust the list in front of you, so you had to double check dates by hand or work around the filter to find the right samples. A filter that quietly drops a second condition or shifts the day makes routine searches slower and leaves room for the wrong records to be acted on.

What changed?

The custom date filter now returns exactly the day you select, keeps combined filters working together, and applies the correct time zone across every status tab. Records saved at midnight are included, and combining the Production Date filter with native date filters such as Published, Collected, and Received returns the right days.

What will you notice in practice?

When you filter by Production Date, you see only the samples from the day you chose, and you can combine it with other filters and still get complete, accurate results in every tab.

Before vs. Now

Before: The Production Date filter could return the wrong day, ignore a second filter, and shift dates across the status tabs. You had to verify results by hand.

Now: The filter returns the exact day, keeps combined filters working, and shows the correct dates in every tab.

#123530

🚀 Improvement

A cleaner Home screen without the notice board panel

What was happening?

When you opened the Home screen in myLIMS Web, a notice board and surveys panel loaded every time. The surveys and notices have moved to another platform, so the panel showed content that was no longer maintained there.

Why was this a problem?

A panel that loads content you no longer use adds clutter to the first screen you see each day and one more thing to load before you get to work.

What changed?

The notice board panel has been retired from the Home screen. myLIMS Web no longer loads it when you open the Home screen.

What will you notice in practice?

The Home screen opens cleaner and goes straight to your work, without the notice board section. Nothing you rely on is lost, since the surveys and notices are now handled on another platform.

Before vs. Now

Before: The Home screen showed a notice board and surveys panel that loaded content now kept on another platform.

Now: The Home screen no longer includes the notice board panel and opens focused on your work.

#125070

07/14/26 · 9:00 PM to 11:00 PM (UTC)

July 14, 2026

myLIMSweb | Version 4.7.648

This release brings a set of fixes and improvements to your daily work in myLIMS Web. Below is what changed and what you will notice in practice.

🔧 Fix

Scheduled sample and activity generation no longer creates duplicates

What was happening?

You set up samples and activities to be generated automatically in advance through the scheduler, and once in a while the same sample or activity was created more than once. Each duplicate came in with its own new ID, so at first glance the records looked normal, even though the schedule was set to create them only once.

Why was this a problem?

Duplicate samples and activities meant extra records to find, review, and remove by hand, and they put the accuracy of your data at risk. Because the duplicates appeared only occasionally, you could not always predict when a clean up would be needed, which added uncertainty to work that should simply run on its own.

What changed?

Scheduled generation now protects against creating the same sample or activity twice, even when several generations are triggered close together. Before a record is created, the system checks again against a fresh reading to confirm it does not already exist.

What will you notice in practice?

Samples and activities scheduled for automatic advance generation are created exactly once, following the settings you configured. There are no duplicate records to track down and remove.

Before vs. Now

Before: Scheduled advance generation could occasionally create the same sample or activity more than once, each with its own ID. You had to find and remove the duplicates by hand.

Now: Scheduled advance generation creates each sample and activity only once. Your records stay clean, with no manual clean up.

#123574

🔧 Fix

The Production Date column filter now returns the exact day and works with other filters

What was happening?

On the Samples screen, you filtered by the custom "Production Date" column and the results did not match the day you selected. The filter could bring records from the following day and skip records recorded exactly at midnight. When you combined "Production Date" with a second filter, the second one was often ignored, and the status tabs, such as Not Received, Received, Not Finalized, Finalized, and Published, could return the previous day.

Why was this a problem?

You could not trust the list in front of you, so you had to double check dates by hand or work around the filter to find the right samples. A filter that quietly drops a second condition or shifts the day makes routine searches slower and leaves room for the wrong records to be acted on.

What changed?

The custom date filter now returns exactly the day you select, keeps combined filters working together, and applies the correct time zone across every status tab. Records saved at midnight are included, and combining the Production Date filter with native date filters such as Published, Collected, and Received returns the right days.

What will you notice in practice?

When you filter by Production Date, you see only the samples from the day you chose, and you can combine it with other filters and still get complete, accurate results in every tab.

Before vs. Now

Before: The Production Date filter could return the wrong day, ignore a second filter, and shift dates across the status tabs. You had to verify results by hand.

Now: The filter returns the exact day, keeps combined filters working, and shows the correct dates in every tab.

#123530

🔧 Fix

Sample requests in the Portal now accept dates with a two digit year

What was happening?

When you requested a sample in the Portal and typed a date with a two digit year, for example 06/07/26, the Portal read it as the year 0026 instead of 2026. Because that date could not be processed, the sample request failed and the sample was not created.

Why was this a problem?

A date typed the way people write it every day quietly broke the request, so you had to notice the failure, correct the year to four digits, and submit again. That turned a simple entry into a repeated step and could delay getting samples into the system.

What changed?

The Portal now interprets dates with a two digit year correctly, so 06/07/26 is understood as 06/07/2026, and it continues to accept dates written with four digits. The century is worked out from the current year, so short dates are expanded to the right year.

What will you notice in practice?

You can type a collection date with either a two digit or a four digit year when requesting a sample, and the request goes through without an error.

Before vs. Now

Before: A two digit year was read as the year 0026 and the sample request failed. You had to retype the date with four digits and try again.

Now: Two digit and four digit years are both accepted, and the sample request is created the first time.

#126891