Journal entries apps: need advice

[Voltes]

Hello everyone,

I want to create an apps like a journal entries, and need some advise or guidance on what do I need and what should I do to achieve that.

The apps I want to create is an Stock count journal, which in then end I would like to create journal in Dynamics 365 F&O. So in my mind, this apps will do these steps:

1. 1st screen, I need to select Warehouse, Location, and the journal name

2. 2nd screen, there is a barcode scanner which will scan the item, and this will create data rows like in a list contains the item number and the quantity.

3. All those list will goes or save to CDS.

4. There is another menu, probably in the 1st screen to push those records in CDS to D365 F&O to create inventory journal there.

What I did so far are :

1. Create tables Warehouse, location, journal type, and the table to records all the counting result (lets call it CountEntries) in CDS.

2. the 1st screen is created, data source is the CountEntries, so I display the Warehouse, Location, and Journal type which is a lookup.

3. the 2nd screen is created up to Barcode scanner button.

and currently I'm confuse on how to bring the Barcode scanner result to a gridlist which is maybe a "Data table" control. Can it create a new record everytime I scan, and the information of warehouse, location, and journal type follows what's in 1st screen ? So when I scan 3 (three) times, the grid / data table control will have 3 rows of item and quantity with in background the row also fill in by warehouse, location and journal type from the 1st screen automatic.

The grid and also the CountEntry table which I imagine will be something like this :

.. and there is also one important thing which I still don't know how to handle it, is on that table has primary key (usually with fieldname "Name") which I don't know what to fill in ? can it be a number sequence, and how to do that ?

Anyone know a good reference to it, with the steps needed to create this. Or just some advice what do I need to do to achieve this.

Many thanks in advance.

TZ

[Voltes]

Hi Kris,

Thanks. it works. So I did use the primary field of the Lookup Entity (master).

However the Default thing is not working, I still need to touch/select the only one record in gallery to make my item having value.

But this is not a big deal, unless to resolve a curiosity how to make it automatically selected. One bigger problem is the patch is not working, as it throw error saying that my CDS expected the type of Record, yet it found type : Text.

I tried to go back to the Collect and try out to use back the one the return GUID, but it also throw error saying expected is Record, and found type is : GUID.

Here is what it's like, I try to Patch 2 field first, 1 for Id, 1 for Site.

ForAll(colEntry,
Patch('App Countings',
Defaults('App Countings'),
{
    Name:CountRows('App Countings') + 1,
    Site:Site
}

and the error after I tried to use back the GUID:

Site it self is the column name of my Entity in CDS, which I'm using and want to insert.

Found some resources : https://powerusers.microsoft.com/t5/Building-Power-Apps/Patch-a-CDS-Lookup-column-within-PowerApps/m...

saying I should put Lookup on that Patch, but I have error: Incompatible type for the condition  or the specified column " _ " does not exist->

ForAll(colEntry,
Patch('App Countings',
Defaults('App Countings'),
{
    Name:CountRows('App Countings') + 1,
    Site: LookUp(Sites, Name = Site)
   
}

Sites is the Data source name found in the treeview

Name (supposedly) is the primary field (key) of entity Site

Site (supposedly) is the field of the collection ColEntry.

Thanks again,

V

[Voltes]

Hello everyone,

Does anyone has some idea or other approach than to use Lookup for that Patch ? Because it seems very difficult to make sure we're choosing the right field name on that Lookup statement. The suggestions somehow mixed with any sources that inside your (my) apps.

It is worsen if we have same field name in each of our data sources, but I can't see that is a bad thing, in fact it is the best practice, right? it will be confusing (and bad) to have different naming for same purpose of field.

Any help will be much appreciated.

Thanks,