Skip to content

Aeon Known Issues

← Atlas Systems

Search known issues

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

51 results found

  1. Null username error occurs when using the Clone to Current User option from a request list

    In Aeon Client v5.2.4, using the Clone to Current User button from a queue's request list will result in a pop-up error stating "An exception occurred while attempting to clone the selected requests: Value cannot be null. Parameter name: Username"

    Workaround: Open an individual request and use the Clone to Current User option from the Request form or select the Clone to New User option from the request list and then select the current user's username from the search.

    Bug# 26834

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  2. Request callslips cannot be printed from an Activity record if custom fields are defined

    Using the Print Callslips button on an Activity record results in an "invalid merge field" error if any custom fields are defined in the CustomFieldDefinitions table.

    Bug# 26639

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  3. System alerts in Aeon Client do not check for emails with the Appointment EmailType

    Emails with the EmailType “Appointment” do not display in the System section of the Aeon Client dashboard.

    Bug# 26272

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  4. Invalid End Date can be entered on the Appointment form in Aeon Client

    Manually confirming or unconfirming an appointment via the Appointment form in the Aeon Client will save any other changes made to the information on the form without enforcing data validation, which can lead to the following error loading appointments in the Client if an invalid End Date was entered and saved:

    “Error refreshing appointments
    Error in the End mapping
    Some appointments could not be loaded. Please contact support.”

    Bug# 26376

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  5. Aeon Client throws error loading appointments if the casing for a username is inconsistent between the User record and Appointment record

    If a username uses different casings in the database between the User record and an Appointment record for that user, this will cause an error when loading the appointment calendar in the Aeon Client that states: "Error in the PreferredName mapping."

    This mismatch can happen if:
    1. A request is cloned to a user via the Clone Request to Another User option in the Aeon Client and a different casing for their username is typed into the Username field on the closing interface.
    2. An appointment is then created for that user from the cloned request using the different username…

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  6. Creating requests from file fails when custom fields are included

    Creating requests from a spreadsheet file in the Aeon Client will fail when user-defined custom fields are included in the spreadsheet.

    Bug# 23597

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Staff Client  ·  Admin →

  7. Applying service packages to photoduplication requests causes errors

    Global service packages cannot be applied to photoduplication requests in the Aeon Client and will result in an error. Non-global service packages may also result in an error when applied.

    Workaround: Apply a global service package to trigger the error, then apply a non-global service package to the request. This will allow the non-global service package to be applied. There is currently no workaround for applying global service packages to requests.

    Aeon 5.2.

    Bug# 23473

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  8. Color contrast issues on the Aeon Options form when using certain skins

    The panel on the left of the Options form in the Aeon Client does not change color based on the Client skin selected and the links on the Resources tab have poor color contrast when using the Office 2016 Dark skin.

    Bug# 22246

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  9. Formatting error in Aeon Client log entry when user is set to away

    The following formatting error will appear in the Aeon Client log when a user signed into a reading room is set to away:

    INFO AtlasSystems.Aeon.FormDashboard - <log4net.Error>Exception during StringFormat: Input string was not in a correct format. <format>Setting user {)} to away.</format><args>{username}</args></log4net.Error>

    Bug# 19730

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  10. Appointment name can't be edited in the v5.1.8 Aeon Client

    Edits to the name of an appointment will not be saved when attempting to make changes in the Aeon Client.

    Note that this issue only affects Aeon Client v5.1.8.

    Bug# 19121

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Staff Client  ·  Admin →

  11. Aeon Client Options form controls are incorrectly aligned

    The controls located within the Aeon Options form in the Aeon Client are not aligned properly within the borders of each section of options on this screen.

    Bug# 18418

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  12. Attempting to edit an appointment with invalid data throws errors

    Appointments containing invalid data will still appear on the User form and within the Appointment control on the Request form, but the Aeon Client will be unable to open the Appointment form and will throw an unhandled exception error when attempting to edit the appointment:

    ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.

    Bug# 17378

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  13. Rescheduling an existing appointment in the Aeon Client may result in an error if the same appointment is also being edited elsewhere

    Editing the Start Date or End Date of an appointment via the Appointment form in the Aeon Client may result in the following error if the appointment was simultaneously edited elsewhere:

    ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
    DevExpress.XtraScheduler.Internal.ActualMappingException: Error in the End mapping

    Bug# 17181

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  14. Aeon Client dashboard does not properly handle database connection errors

    The Aeon Client dashboard will correctly catch database connection errors, but will then attempt to use the connection, which causes an additional error.

    Bug# 17093

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  15. Multithreading error during Aeon Client dashboard refresh

    The following error can sometimes occur in the Aeon Client logs upon a dashboard refresh and may lead to Client slowness:

    ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
    System.InvalidOperationException: A multithreading issue is detected. The DevExpress.Data.CurrencyDataController.DisableThreadingProblemsDetection option allows you to disable the exception, but it does not resolve the underlying issue.
    ManagedThreadId: 20; ThreadName: ''

    Bug# 16762

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  16. Custom fields are highlighted yellow when added to a custom tab group in the Aeon Client

    Custom fields defined in the Aeon Customization Manager's CustomFieldDefinitions table will display highlighted yellow if added to a custom tab group created on a form in the Aeon Client.

    Bug# 15993

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  17. Leaving FutureRoutingDays customization key blank causes errors

    If the FutureRoutingDays customization key value is blank, the following error will occur when attempting to import requests from file:

    ERROR AtlasSystems.Aeon.FormCreateRequests - An error occurred when creating the requests: Input string was not in a correct format.

    Bug# 15791

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  18. Appointments can't be saved using the request form's appointment control if system time zone is UTC

    If the system time zone is set to UTC, the following error is logged when attempting to save an appointment with the appointment control on the request form:

    ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
    System.ArgumentException: The conversion could not be completed because the supplied DateTime did not have the Kind property set correctly. For example, when the Kind property is DateTimeKind.Local, the source time zone must be TimeZoneInfo.Local.

    Note: This only applies to the system time zone labeled simply as "Coordinated Universal Time," and not other time zones with no UTC offset. It does not occur when both…

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  19. Errors that prevent the appointment scheduling tool from loading also affect other areas of the Client

    If an error prevents the appointment scheduling tool in the Client from loading, this will also cause other areas of the Client to become unusable until the underlying error is resolved.

    Bug# 15330

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  20. Aeon Client becomes unusable if an appointment is created with an invalid username

    If an appointment is created with an invalid username, this will prevent both the appointment scheduling tool and other parts of the Client such as the list of queues from loading.

    Note: If you experience this bug, please submit a ticket for Atlas Support to resolve the underlying invalid data issues.

    Bug# 15329

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →
← Previous 1 3

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)