You need to resolve the issue reported during testing.
What should you do?
You need to resolve the issue reported during testing.
What should you do?
Creating a relationship within the Inspection Order table to the originating inspection order is the best solution for resolving the issue reported during testing. This approach allows linking the new inspection order (created for re-inspection) to the original one, enabling access to and view of the photos taken during the previously failed inspection. It ensures that inspectors can fill in findings comments and upload at least one photo for any inspection step that is marked as failed, thus addressing the requirement of potentially having multiple images for different inspection steps within a single inspection order.
Create relationship
The answer explanation provided has nothing to do with the Case Study issue. The question has to do with failed inspection photos not employee photos. The answer is B
Users should be able to upload multiple files, therefore the relationship is either not created, or testers do not have access to that table
B: While I do agree with peterwilliams that it would seem odd they didnt notice the issue earlier since these 2 tables would not be related without the relationship, the other options do not make sense. 1. It states clearly that each STEP (not order) should have an image 2. In what form are they on? and how does a quick view of the Order, which doesnt capture images help..
Option A is not the best choice because creating an image data type within the Inspection Order table would only allow storing a single image for the entire inspection order. However, the requirement states that inspectors must fill in findings comments and upload at least one photo for any inspection step that is marked as failed. This implies that there could be multiple images for different inspection steps within a single inspection order. Option B, on the other hand, creates a relationship within the Inspection Order table to the originating inspection order, which allows linking the new inspection order (created for re-inspection) to the original one. This way, the photos taken during the previously failed inspection can be accessed and viewed in the new inspection order, resolving the issue reported during testing.
Answer is probably correct. If answer was B, the solution would be so broken that it is very unlikely that this issue would be raised ahead of more serious ones. It all depends on how the photos are being stored.
Relationship is required to view related record
i am not english native: "Support the ability to store 'photo references' within each inspection step to document defects found during inspections." is the photo itself a reference or could it be a reference LINK to the photo, because with high volume I would not save the images (potential consuming valuable dataverse space) to the entity. In a next step if photo reference could be the link you could use the 'quick view form' to display the link reference to the photo. Maybe it is C? (but, of course, there exists: File and Image Allows you to store file and images inline in Dataverse. Lets save the 3 'lord of the ring' films in best quality to dataverse ;-) )
for quick view form, you would first need to have a referenced record. First B, then c.
After consulting bing ai web search and chatgpt (which is quite ok on microsoft topics) I tend to vote A. Perhaps we overthinked this question while thinking this might be a B.
Sorry, actually bing ai web search says it's B. Perhaps it is.