Hide column in a form based on value in another list

Question

I'm using SP 2013. I have 2 lists, Camps and Activities, that both have a CampID field. The Activities list has a Yes/No field. When I display the edit form for Camps, I need to see if the Yes/No field in Activities for that camp is set to No. If it is, don't display (or disable) some of the fields in the Camps Form. Is there a way to do this without a custom coded solution? I do have SP Designer at my disposal but I'm looking for the simplest solution.

Answer 1

You can take inspiration from here: Limit only one entry per day per user in sharepoint list

In short:

• Display an Activities View on the Edit Form
• Use JavaScript (in a Calculated Column) to alter your Edit Form

Answer 2

If by "without a custom coded solution", you mean no server-side compiled/deployed code, then yes -- but your solution will almost certainly require some JavaScript code added to the EditForm for your Camps list.

• First, create a variable to flag whether activities are allowed or no, defaulted to false (e.g. var areActivitiesAllowed = false ) Next, perform a JSOM/CSOM lookup for the corresponding item in the Activities list (see MSDN doc and example)
• In the onQuerySucceeded, set your areActivitiesAllowed flag to the Yes/No field value from the Item you looked up.
• Then if the areActivitiesAllowed is true, hook up a jslink template to make a read-only representation of the column:

if (areActivitiesAllowed) {
  fldCtx.Templates = {};
  fldCtx.Templates.OnPostRender = hiddenFieldsOnPostRender;
  fldCtx.Templates.Fields = {
    'InternalNameOfFieldToDisable1': { 'EditForm': makeFieldReadOnly },
    'InternalNameOfFieldToDisable2': { 'EditForm': makeFieldReadOnly },
    'InternalNameOfFieldToDisable3': { 'EditForm': makeFieldReadOnly }
  }
}

function makeFieldReadOnly(ctx) {
    // this is where you would normally return
    // custom field rendering html -- by just returning
    // the plain text value, it is effectively readonly text on the page
    return ctx.CurrentFieldValue;
}

Note: that while this will disable the fields on the page, it is not controlling permissions to those fields. Power users could still write their own CSOM code on their own local machines to edit the apparently disabled fields. Only an EventReceiver (custom code) could truly prohibit the field from being changed by surreptitious means.