Latest Contributions by SteveRichards4

Hi Sarah, I have managed to attach the solution to my reply now - I was struggling with that yesterday. I have linked it here as well. https://community.esri.com/servlet/JiveServlet/download/223329-1-205569/SX_Test_Sig_FINAL.xlsx The key to getting it working is that the Feature Service for the main layer must have a field with _count at the end: Here is the schema for my main layer: Layer: SX_Test Fields: Name ( type: esriFieldTypeString , alias: Name , editable: true , nullable: true , length: 50 ) Location ( type: esriFieldTypeString , alias: Location , editable: true , nullable: true , length: 50 ) GlobalID ( type: esriFieldTypeGlobalID , alias: GlobalID , editable: false , nullable: false , length: 38 ) created_user ( type: esriFieldTypeString , alias: created_user , editable: false , nullable: true , length: 255 ) created_date ( type: esriFieldTypeDate , alias: created_date , editable: false , nullable: true , length: 8 ) last_edited_user ( type: esriFieldTypeString , alias: last_edited_user , editable: false , nullable: true , length: 255 ) last_edited_date ( type: esriFieldTypeDate , alias: last_edited_date , editable: false , nullable: true , length: 8 ) OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID , editable: false , nullable: false ) SignNow ( type: esriFieldTypeString , alias: SignNow , editable: true , nullable: true , length: 500 ) SX_Test_Actions_count ( type: esriFieldTypeString , alias: SX_Test_Actions_count , editable: true , nullable: true , length: 500 ) #It kept saying my field length was too short 500 is probably too big ☺ The layer for the attachments (signatures) is: Layer: SX_Test_Actions Fields: parentGlobalID ( type: esriFieldTypeGUID , alias: parentGlobalID , editable: true , nullable: true , length: 38 ) ActionName ( type: esriFieldTypeString , alias: ActionName , editable: true , nullable: true , length: 50 ) GlobalID ( type: esriFieldTypeGlobalID , alias: GlobalID , editable: false , nullable: false , length: 38 ) created_user ( type: esriFieldTypeString , alias: created_user , editable: false , nullable: true , length: 255 ) created_date ( type: esriFieldTypeDate , alias: created_date , editable: false , nullable: true , length: 8 ) last_edited_user ( type: esriFieldTypeString , alias: last_edited_user , editable: false , nullable: true , length: 255 ) last_edited_date ( type: esriFieldTypeDate , alias: last_edited_date , editable: false , nullable: true , length: 8 ) OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID , editable: false , nullable: false ) Email me at srichards@hnrg.com <mailto: srichards@hnrg.com > if you can’t download the file Steve ... View more

Hi James, That did the trick, Thanks very much for your help. I will attach the final solution. Steve ... View more

Hi James, Thanks for your response. The Feature Service does have a related table with attachments - this is for the signatures. I have republished the service and removed the periods. I can publish the survey and it works i.e Fill in the top part of the form Submit Retrieve from Inbox Sign Submit The signature saves as expected in the attached Feature Class - if you sign first time around it does not get retrieved from the inbox - this is documented and expected, I am not going to make the signature field available until it has been submitted once. As I am using a repeat to hold the signature - I want to limit the repeats to 1 so it only gets signed once. As soon as I try and limit the repeats to 1 then I get the publishing error Looks like this: Remove the repeat limit and publish Steve ... View more

I think you have your answer but for what it's worth I had some issues trying to implement nested if statements, they worked in excel but not in the Survey. I actually found it useful for my brain (and to get it working) to break the problem down into separate 'calculate' lines, calculate is a special field type that does not display on the form it works just like a variable and can be used in the other calculations e.g type,name,label,calculation 1/ calculate,dia_diff,Diameter Difference,${sec_6_log_dia_meas_len}-${sec_6_log_dia_disp_len} 2/ note,sec_6_log_dia_diff,Measured Difference (mm),if(${dia_diff}<0,${dia_diff} * -1,${dia_diff}) 3/ calculate,dia_diff_score_low,Diameter Score < 400,if(${sec_6_log_dia_disp_len}<400,if(${sec_6_log_dia_diff}>25,0,3),3) 4/ calculate,dia_diff_score_high,Diameter Score >= 400,if(${sec_6_log_dia_disp_len}>=400,if(${sec_6_log_dia_diff}>50,0,3),3) 5/ integer,sec_6_log_score,Log Score,min(${len_diff_score},${dia_diff_score_low},${dia_diff_score_high}) The logic is: 1/ Calculate the difference between what is measured and what the machine displays 2/ Convert the measurement to an absolute value (ABV) 3/ If the log has a diameter under 400mm and the difference in measurement is >25mm this log scores a 0 4/ If the log has a diameter over 400mm and the difference in measurement is >50mm this log scores a 0 5/ The log score is the minimum of Length Score,Small Diameter Score or Large Diameter Score I left out the log length score calculations but they are similar to diameter I have attached the full survey if anyone wants to take a look - I have trimmed out a lot of the lookup data. Steve ... View more