Cannot edit custom fields of named file set

LabKey Support Forum (Inactive)
Cannot edit custom fields of named file set fcf  2017-06-02 12:01
Status: Closed
 
This appears to be a bug in Labkey 17.1.
The server is setup with CentOS 7.3.1611, PostgreSQL 9.5.7, Tomcat 8.0.37, Java 1.8.0

Steps to reproduce:
1. Go to a project. On the portal tab, add a Files web part.
2. Choose customize off the dropdown list next to the word Files.
3. Pick Configure File Roots
4. Create a named file set with a root different than the default.
5. Choose the new file root to be the new file set
6. Click on the admin cog, then the "File Properties" tab, "Use Custom File Properties"
7. Create a few custom file properties. Click Submit.
8. Right click a file and select "Edit Properties". Click Save.

RESULT: The edits will not be saved. The edits WILL be saved if the default file root is used, just not for a customized file set. No errors are generated in any log.
 
 
Jon (LabKey DevOps) responded:  2017-06-02 15:14
Hello,

I'd like to get some clarification here in your repro steps.

Once you're at Step 4, I'm assuming you mean you're on the "Administer File System Access" page and you added a file set there by entering in a Name and Path. Is that correct?

What do you mean in Step 5 where you say "Choose the new file root to be the new file set"? Are you talking about changing the actual file Root by then clicking on "Configure file root for Project." and then selecting "Use a project-level file root" and entering the path you used previously in Step 4?

Regards,

Jon
 
fcf responded:  2017-06-02 15:51
Clarifications:

Step 4: I am on the "Administer File System Access" page. I click "Add File Set". I enter a name and an absolute path to where I want to keep my files.

Step 5: Return to the project portal. Click the dropdown list next to the word Files and select Customize. On the Customize Files page, clieck the dropdown next to File Root and select the new file set that you created.
 
Jon (LabKey DevOps) responded:  2017-06-02 23:12
Thank you for the clarification. I've confirmed the behavior.

The API does show the value, so the issue is how the webpart is rendering the data.

I'll have a bug created on this and investigated further.

Regards,

Jon
 
Jon (LabKey DevOps) responded:  2017-06-02 23:26