Added an intermediate page for accessing camera in V2 extensions

[defr0std]

A request is made to use camera feature in V2 extensions.
microsoft/AL#215

The problem is that Camera API requires .NET variable which can be used only on pages. Therefore the proposed solution is to add an intermediate page which would access the camera and provide the taken picture back to the caller as a BLOB.

This solution requires the same number of clicks for the picture to be taken, but shows an intermediate form in the process. On one hand, this form could be a bit distracting, but on the other hand, this form will also report an error message if the camera is not available, so there is no need to check for that in every use case of the camera API and hide the buttons.

The form can also be customized by the extension to provide more instructions to the user.

This is how a picture could be taken using V2 code:

pageextension 50108 CustomerListExt extends "Customer Card"
{
    actions
    {
        addafter(Approval)
        {
            action(ChangePicture)
            {
                ApplicationArea = All;

                trigger OnAction();
                var CameraPage : Page "Camera Interaction";
                    PictureStream : InStream;
                begin
                    CameraPage.AllowEdit(true);
                    CameraPage.Quality(100);
                    CameraPage.EncodingType('PNG');

                    CameraPage.RunModal();

                    if (CameraPage.GetPicture(PictureStream)) then begin
                        Image.ImportStream(PictureStream, CameraPage.GetPictureName());
                    end;
                end;
            }
        }
    }
}

P.S. This is a bit non-standard request - no tests are added since it's all integration API, no codeunits either :)

[defr0std]

Perhaps a codeunit is also needed to expose IsAvailable method.

[JesperSchulz]

This is a fine little functionality, but it needs some refactoring. We should not have this much code on a page. We will take a closer look and do a little refactoring and re-design.

[defr0std]

@JesperSchulz Thanks. Also got some UX feedback that it would be nice to have only one OK button on the intermediate page instead of OK/Cancel. Could you please also have a look that while refactoring?

[MarcHansenMicrosoft]

Try using Evaluate to get the string value of the enumeration.

[defr0std]

Moved properties to the page itself, removed options.

[MarcHansenMicrosoft]

Better do
IF NOT CameraAvailable THEN
EXIT;

[defr0std]

Done.

[MarcHansenMicrosoft]

Use blob.Import(filename)

[defr0std]

Done

[MarcHansenMicrosoft]

Just Call them Picture and PictureName

[defr0std]

Not relevant anymore.

[MarcHansenMicrosoft]

If you end up saving this you should have a better key. A GUID will do.

[defr0std]

Table removed

[MarcHansenMicrosoft]

Us QueryClose to return the LookUpOK if you got a picture.

[defr0std]

Not possible, as discussed. Instead added GetPicture(stream: InStream): boolean, as agreed.

[MarcHansenMicrosoft]

Please make sure to update the usage sample to reflect the changed code.

[JesperSchulz]

Addressed through pull request #44. Case closed.

[DmitryKatson]

@JesperSchulz i've just tested this in wave 2 with iPhone and found that
if (CameraPage.GetPicture(PictureStream))
shows the import screen to take the picture once again.

So CameraPage.RunModal()
gives me this screen

and then I see

That's because CameraPage.GetPicture have FileManagement.BlobImport() inside

And FileManagement.BlobImport() has UploadIntoStream

which opens this new step in the iPhone.
I found this interesting "remark" in the documentation https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/file/file-uploadintostream-method

But i think it's not longer true...

So, you need to change "Camera iteraction".GetPicture business logic.

[JesperSchulz]

@dkatson, thanks for letting me know! I'll see what i can do ;-)

[srkkoneti]

@JesperSchulz, We have tested the camera feature in Wave2 the same issue occurring, After uploading screen, showing blank import screen and if we cancel the import screen, we are getting following error

[JesperSchulz]

We've actually not been able to get around to this issue yet. There are currently quite a few more pressing tasks we need to attend to, I'm afraid. But I've created a bug for this and we should be able to get to it soon. If you'd like to suggest a fix, please go right ahead :-) That might just speed up things! Otherwise please have a little more patience.

[DmitryKatson]

Well, that was my workaround.

local procedure TakePicture(var TempPurchLine: Record "Purchase Line" temporary);
var
    //CameraInteraction: Page "Camera Interaction";
    PictureStream: InStream;
    FileManagement: Codeunit "File Management";
    TempBlob: Codeunit "Temp Blob";
    FileName: Text;
begin
    //CameraInteraction.AllowEdit(true);
    //CameraInteraction.Quality(100);
    //CameraInteraction.EncodingType('PNG');
    //CameraInteraction.RunModal();
    //if (CameraInteraction.GetPicture(PictureStream)) then begin
    //    TempPurchLine."AIR Item Photo".ImportStream(PictureStream, CameraInteraction.GetPictureName());
    //end;

    FileManagement.BLOBImport(TempBlob, FileName);
    TempBlob.CreateInStream(PictureStream);
    TempPurchLine."Item Photo".ImportStream(PictureStream, FileName);
end;

[DmitryKatson]

So, just completely ignore Page "Camera Interaction". It works, but not so sexy as with "Camera Interaction" :)

[JesperSchulz]

Module extracted. Please take it for a spin :-) https://github.com/microsoft/ALAppExtensions/tree/master/Modules/System/Camera%20and%20Media%20Interaction

[srkkoneti]

@JesperSchulz , Could you please let us know in which build it was included

[JesperSchulz]

The code went in just before Christmas on the 22nd of December. If you take the latest preview build of version 16, you should get it. The code was also backported to 15, but release usually takes a little while. Expect the change to be released by EOM.