Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter sgflynn

    (@sgflynn)

    Hi Peter, that’s great to hear. I look forward to the updated version.

    Thanks

    Steve

    Thread Starter sgflynn

    (@sgflynn)

    Hi Peter,

    Thanks for the quick reply.

    I’m running version 5.3.0 but the problem remains.

    Here’s some things I’ve tried:

    Different browsers, changed themes, disabled all other plugins but same problem

    To try to rule out an issue with the table design I replicated the problem with a very simple data model with three tables as follows:,

    CREATE TABLE product
    (product_id int NOT NULL auto_increment
    ,product_name varchar(20) NULL
    ,PRIMARY KEY (product_id)
    ) ENGINE InnoDB DEFAULT CHARACTER SET utf8mb3 COLLATE=utf8mb3_unicode_ci;

    CREATE TABLE customer
    (customer_id int NOT NULL auto_increment
    ,customer_name varchar(20) NULL
    ,PRIMARY KEY (customer_id)
    ) ENGINE InnoDB DEFAULT CHARACTER SET utf8mb3 COLLATE=utf8mb3_unicode_ci;

    CREATE TABLE sales
    (sales_id int NOT NULL auto_increment
    ,product_id int NULL
    ,customer_id int NULL
    ,PRIMARY KEY (sales_id)
    ) ENGINE InnoDB DEFAULT CHARACTER SET utf8mb3 COLLATE=utf8mb3_unicode_ci;

    I created a template for table sales with lookup autocomplete relationship between customer_id and customer.customer_id and another lookup automcomplete relationship between product and product.product_id.

    I added two rows of data to the customer table and two rows to the products table.

    I created a project with a single form to add sales. The form has the lookups for product and customer. Whichever lookup field appears first on the form has the “Not Authorized” error. If I swap the lookups around, the error still occurs on the lookup which occurs first in the form.

    This was the simplest design I could implement to test the issue.

    Thanks

    Steve

Viewing 2 replies - 1 through 2 (of 2 total)