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

myLIMSweb | Version 4.7.646

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

You can attach files with more than one period in the name again

What was happening?

You went to attach a file to an activity, chose a document named with a date or a business reference such as RA 6624.2026 COC WALM.pdf, and the upload was rejected. The file looked perfectly valid to you, yet the system refused it. Replacing the period with another character let it through, which was confusing and inconsistent with how you name your files.

Why was this a problem?

You had to rename files to get them into the system, which slowed down routine work. For laboratories whose integrations attach files automatically, the rejected uploads interrupted an unattended process and required someone to step in and fix names by hand.

What changed?

Files whose names contain more than one period can be attached normally again. Files with genuinely unsafe types are still blocked, so your environment stays protected.

What will you notice in practice?

Your existing file names work as they are, with no renaming. Automated attachment flows run through again without manual correction.

Before vs. Now

Before: Files with more than one period in the name were rejected. You had to rename files or fix automated flows by hand.

Now: Files with multiple periods upload normally. Unsafe file types remain blocked, so protection is unchanged.

#126109

🔧 Fix

Administrators can set their own password again when Identity Center is active

What was happening?

As an administrator, you opened your own user profile to set or update your password, and the password field was greyed out with a message saying the password was managed elsewhere. Because you could not set a local password, sign in to the mobile apps that rely on it stopped working for your account.

Why was this a problem?

You were locked out of the mobile apps through no fault of your own, which interrupted work that depends on mobile access. There was no self service way around it, so the situation created uncertainty and a support request.

What changed?

When you edit your own profile, the password field is now active and you can set your local password. The message about the password being managed elsewhere is hidden on your own profile.

What will you notice in practice?

You can update your own password and sign in to the mobile apps again. Password management for every other user continues to be handled by Identity Center exactly as before.

Before vs. Now

Before: The password field was locked on your own profile. You could not sign in to the mobile apps.

Now: You can set your own local password. Mobile sign in works again, with no change for other users.

#124177

🔧 Fix

Saving samples and activities after changing the Sample Type works without errors

What was happening?

You changed the Sample Type on a sample or activity and tried to save your changes, and the system returned an unexpected validation error that stopped the save. The record looked ready to save, so the error was surprising and left you unsure how to proceed.

Why was this a problem?

You could not save legitimate changes, which blocked routine work on samples and activities. Getting past it often meant manual cleanup, adding rework to a simple everyday action.

What changed?

When documents tied to old automatic generation settings are removed, the system now clears those settings for you. With nothing left pointing to documents that no longer exist, the save completes normally.

What will you notice in practice?

You can change the Sample Type and save without hitting the error. There is no manual cleanup to do, and your records stay consistent.

Before vs. Now

Before: Saving after a Sample Type change could fail with a validation error. You had to clean up settings by hand.

Now: Saving completes normally. Old settings are cleared automatically and records stay consistent.

#124434

🚀 Improvement

Chain of Custody requests now arrive complete and in your language

What was happening?

You submitted a Chain of Custody request from the Portal, and the notification did not always arrive complete, or the activity and message created in myLIMS appeared in a language different from the one you had chosen. If a sample had no collection point, the request could fail to go through at all.

Why was this a problem?

Receiving content in the wrong language created confusion for teams working in Portuguese, English, or Spanish, and incomplete notifications made it harder to act on a request. A request that failed because of a missing collection point interrupted the flow and required a second attempt.

What changed?

Chain of Custody requests now generate a complete request email in all three supported languages. The activity and message created in myLIMS appear in the language of the person who made the request, and requests without a collection point are processed correctly.

What will you notice in practice?

You receive a complete, correctly localized notification for every request. Requests go through reliably, including those whose samples have no collection point.

Before vs. Now

Before: Notifications could be incomplete or in the wrong language, and some requests failed. You had to interpret mismatched content or resubmit.

Now: Complete notifications arrive in your own language. Requests are processed reliably every time.

#122198

🔧 Fix

Chain of Custody messages now show their full content in myLIMS

What was happening?

A Chain of Custody request was submitted from the Portal, and when you opened the Messages tab of the related proposal or sample in myLIMS Web, the message body was empty. The message was there, but the detail that came with the request was missing, so you could not see what had been sent.

Why was this a problem?

An empty message meant you lost the context that accompanied the request, which forced you to look it up elsewhere or ask the requester. That added uncertainty to a step that should be straightforward.

What changed?

The content of the message now transfers correctly from the Portal to myLIMS. The complete message body appears in the Messages tab as expected.

What will you notice in practice?

When you open the Messages tab, you see the full message that came with the Chain of Custody request. There is no missing detail to chase down.

Before vs. Now

Before: The Chain of Custody message body arrived empty in myLIMS. You had to look up the missing detail elsewhere.

Now: The full message body appears in the Messages tab. Nothing is missing to chase down.

#126112

myLIMSweb | Version 4.7.1

🚀 Improvement

• Sample and activity copies now automatically maintain the link to the batch (with a new batch copy option and unit of measure in the master data).

What was happening?
When copying a sample or activity linked to a batch, either in the batch tab or on individual screens:
The user clicked on Copy.
The system created the new sample or activity normally.
The screen did not indicate any problems.

Then, as the flow continues:
The new copy did not appear to be linked to the batch.
The user realized that the information was incomplete.

Why was this a problem?
The copy appeared correct, but required manual adjustment afterward.
It generated rework, mainly due to the need for multiple copies.
This increased the risk of proceeding with the process using incomplete data.

What has changed?
Copying samples and activities now automatically maintains the link to the batch.
In the Batch Samples tab:
You can copy by specifying the desired quantity.

In the Batch Activities tab:
The copy also maintains the link without further action.
The batch will now include the Unit of Measurement field.

How will you notice it in practice?

When copying within a batch, the new sample or activity already appears linked.
It is no longer necessary to review or correct the link.
It is possible to create multiple ready-made copies at once.
The lot displays the unit of measurement along with the quantity.

Before vs. Now
Before:
Copy created without batch link.
Manual linking is required afterwards.

Now:
Copy already created with correct link.
Faster and more direct process #110443

Portal | Version 4.11.0

🚀 Improvement

• Filters will now display full names without cropping on the Portal screens.

What was happening?
When accessing the Reports screen on the Portal and opening the Requesting Account filter, the user had to choose an account from a list.
When accounts had long names, the dropdown displayed those names shortened.
At that time, the system only displayed part of the text, making different accounts appear the same.
The same behavior could also be observed in other parts of the Portal, such as in the Collection Point field in Sample Request and Quick Edit.

Why was this a problem?
Without seeing the full name, the user couldn't be sure which account they were selecting.
This led to repeated attempts, incorrect filter selection, and the need to redo the operation.
In practice, this increased rework and uncertainty in the use of filters.

What has changed?
Selection lists now automatically adjust their width based on the size of the displayed content.
When the text reaches the maximum screen size, it breaks into multiple lines to maintain readability.
The field nomenclature across the Portal screens was also standardized.

How will you notice it in practice?
When opening filters with long names:
The account names appear in full.
The list expands automatically as needed.
When the screen limit is reached, the text is displayed on more than one line.
Identifying the correct account becomes clearer and more straightforward.

Before vs. Now
Previously: names appeared cut off, making identification difficult and leading to errors.
Now: full names are displayed, with automatic adjustment and improved readability #103847

myLIMSweb | Version 4.7.626

🔧 Correction

• The filter with "Allow text" now correctly accepts letters and numbers.

What was happening?
When configuring numeric information (integer or fractional) with the "Allow text" option and using it as a filter on the sample listing screen, the user attempted to type values into the field.
At that time, the system allowed the input of numbers, but when any letter was entered, the field displayed an error indicator and blocked the entry.
This made it appear as if the field was malfunctioning, even though the configuration allowed text.

Why was this a problem?
The behavior conflicted with the configuration defined by the user.
In practice, he believed he could use text and numbers in the filter, but he was prevented from doing so, generating doubt about its operation and hindering the search for samples.
Furthermore, it could lead to incomplete queries or the need to change settings unnecessarily.

What has changed?
The system now correctly respects the "Allow text" setting.
When this option is enabled, the field accepts any type of character.
When not active, the behavior remains exclusively numerical.

How will you notice it in practice?
When using filters in the sample listing:
Fields marked "Allow text" typically accept letters and numbers.
There is no more blocking when typing text.
Fields without this configuration will continue to behave numerically.

Before vs. Now
Previously: the system blocked text even when it was allowed.
Now: the field behaves according to the defined configuration #122242

🔧 Correction

• Source sample selection stops automatically filling in incorrect data.
  

What was happening?
During the results registration process, the user selected a source sample to fill in a specific raw data point.
When making this selection, the system automatically filled in the value not only in the chosen field, but also in other related raw data—even when these belonged to different sample types.
In practice, the user performed an action expecting to update only one field, but saw other fields being filled in without additional intervention.

Why was this a problem?
This behavior generated inconsistencies in the data and forced the user to manually review all affected fields.
In addition to the rework, there was a risk of error if any improperly replicated value was not corrected.
This directly impacted the reliability of the recorded results.

What has changed?
The system now correctly validates the sample type before applying the selected value.
Autocomplete only occurs on the raw data corresponding to the correct type.
The remaining fields remain unchanged.

How will you notice it in practice?
When selecting a source sample:
Only the corresponding field will be filled.
Other raw data will not be automatically altered.
There will no longer be a need to review and correct replicated values.

Before vs. Now
Previously: the value was automatically replicated to multiple incorrect fields.
Now: the value is applied only to the correct field #121999