Handle input value in a repeatin group

krenkel · 2024-12-09T23:57:14.112Z

Bonsoir ici au Brésil - Itajaí - Santa Catarina.
Je vais le traduire en français, je crois que vous êtes français, non ? ; )

Allons-y par parties, je comprends que vous avez deux tableaux :
Tableau 1 - journal quotidien :
Tableau 2 - Évaluation du véhicule

Est-ce que tu aimerais avoir un panneau, où ça montre par exemple que la voiture, par exemple là-bas en France,
une Peugeot 208, plaque d’immatriculation xyz, à la date d’aujourd’hui : 09/12/2024 (jj/mm/aaaa) norme Brésil, avec l’évaluation de :
Depuis votre écran, les données du journal précèdent les données de la voiture.

TB_LOG_DIARY
Commentaire général : texte
Contrôleur : employé
Date : date
Heure de début
Heure de fin : date
Paramètre de l’entreprise : Paramètre de l’entreprise
Paramètre du véhicule : paramètre du véhicule
Itinéraire : liste des paramètres du véhicule
Manager du jour : texte
Signature : texte

TB_AVALIACAO_VEICULOS
Freins : Nombre
pneus : nombre
ceinture de sécurité : numéro
Commentaire : texte
Journal quotidien : Journal quotidien
Paramètres du véhicule : liste des paramètres du véhicule
Photo : Archives
lumières: nombre

D’après ce que j’ai compris, ce journal et l’évaluation deviendront un historique de cette voiture entrant dans votre entreprise, dans notre exemple : Modèle de voiture 208, marque Peugeot, plaque d’immatriculation xyz - identification préalable de la voiture, et nous devons remplir l’autre data , et avec cela, elles seront enregistrées dans la base de données, et d’après ce que je vois, elles sont dans des tables différentes, elles n’ont pas de clé étrangère, qui dans le cas de Bubble, fonctionne comme suit, nous avons la table de journalisation quotidienne , qui a une personne responsable, et nous avons la table évaluation, par exemple, nous aurions la table d’évaluation du véhicule, avec un champ comme le nom de la table du journal journalier, voici une simple connexion de la table d’évaluation à la table du journal quotidien. Avec cette communication, lors de la sauvegarde des données, vous aurez accès à la personne responsable de l’évaluation à travers une seule table, qui sera la table d’évaluation du véhicule. Je ne sais pas si vous me comprenez, mais sur cet écran vous ne me montrez qu’une pop-up à compléter, mais il n’y a pas d’écran avec les données déjà enregistrées par date et heure, puisque vous le ferez quotidiennement , vous devrez avoir un enregistrement par jour, et si vous avez l’enregistrement de la veille, vous contrôlerez cet historique (log) par date, plaque d’immatriculation, modèle, vous pourrez faire beaucoup de choses. mais pour commencer par date. Donc sur le bouton où vous avez d’anciens fichiers, je crois qu’il s’ouvre un écran avec une table et/ou un groupe répéteur qui va charger les données de la voiture évaluée, est-ce qu’il fait cela correctement ?

krenkel · 2024-12-09T23:57:31.721Z

Good evening @ here in Brazil - Itajaí - Santa Catarina.
I’m going to translate into French, I believe you’re French, right? ; )

Let’s take it one step at a time, I understand that you have two tables:
Table 1 - daily log:
Table 2 - Vehicle evaluation

Would you like to have a panel that shows, for example, that the car, for example there in France,

a Peugeot 208, license plate xyz, on today’s date: 12/09/2024 (dd/mm/yyyy) Brazilian standard, with the evaluation of:
According to your screen, the log data comes before the car data.

TB_LOG_DIARIO
General comment: text
Controller: employee
Date: date
Start time
End time: date
Company parameter: company parameter
Vehicle parameter: Vehicle parameter
Route: list of vehicle parameters
Manager of the day: text
Signature: text

TB_VEHICLE_EVALUATION
Brakes: Number
tires: number
seat belt: number
Comment: text
Daily log: Daily log
Vehicle parameters: List of vehicle parameters
Photo: File
lights: number

From what I understand, this log and the evaluation will become a history of an entry of this car in your company, in our example: Car model 208, Peugeot brand, license plate xyz - prior identification of the car, and we have to fill in the other data, and with that it will be saved in the database, and from what I can see, they are in different tables, they do not have a foreign key, which in the case of Bubble, it works like this: we have the daily log table, which has a person in charge, and we have the evaluation table. For example, we would have the vehicle evaluation table, with a field like the name of the daily log table. This is a simple connection from the evaluation table to the daily log table. With this communication, when saving the data, you will have access to the person responsible for the evaluation through just one table, which will be the vehicle evaluation table. I don’t know if you understand me, but on this screen, you are only showing me a pop-up that needs to be filled out, but there is no screen with the data already saved by date and time. Since you will do this daily, you will have to have a record per day. And if you have the record from the previous day, you will control this history (log) by date, license plate, model. You can do a lot of things, but to start by date. So, on the button that you have old files, I believe that there opens a screen with a table and/or a repeating group that will load the data of the evaluated car. Does it do this correctly?

julian_ski · 2024-12-10T08:28:20.096Z

Nice to meet you. Yes, I’m from Paris. It’s a pleasure to talk to you in Brazil. It’s OK to speak in english, i translate myself

Indeed, the ideal would be that on the page that I showed you in screenshot is displayed the history of the last control. That would save time.

On the historical part, the idea was not to open a repeating group but a PDF file that will have been saved before by clicking on my save button.

The whole difficulty is to have a repeating group that displays all the vehicles but only one input per control point to indicate the state of the vehicle. When saving, I can’t make my input (the one in my first line of the repeating group) multiply and capture the value of each of the lines.

So I tell myself that my method is perhaps not the right one.

I put a photo of my page under construction maybe it can help: a line with an input for the lights, an input for the brakes, … which multiplies according to the number of vehicles but with the name of the input which remains the same…

Capture1382×523 51.9 KB

Do you think I should create a database per vehicle?
Maybe that would be easier for my workflow then?

krenkel · 2024-12-10T11:56:39.058Z

It’s a pleasure to meet you - my name is Nestor.
Good morning, I’m going to create a test project, and I’ll get back to you soon to see how we’re doing with this idea of yours. But no, don’t create a database for each vehicle, you’ll have these two tables that you already have, this is a start. I’ll be back soon with something on screen. See you soon.

julian_ski · 2024-12-12T09:06:18.909Z

No problem Nestor, I continue to look for solutions on my side as well of course.

julian_ski · 2024-12-17T13:53:45.217Z

Hello Nestor,

were you able to look at my problem?

thanks

krenkel · 2024-12-17T21:57:09.141Z

Hi @julian_ski, still dwarf, have you made any progress?

julian_ski · 2024-12-18T08:14:02.552Z

Unfortunately I still haven’t found the solution. Every time I get the same result, taking into account only one car and not all of them…

krenkel · 2024-12-18T10:52:16.380Z

Hi @julian_ski, I’ll send you a printout in Excel, to see if this is what you want. That is to have a vehicle and keep the history of just one vehicle, but it’s in this idea, because I launch a car and then I’ll just launch its daily evaluations. And this will be for as many vehicles as you have. Is this the idea you want?

julian_ski · 2024-12-18T11:06:16.273Z

That’s it. And this information is contained in a sheet per day with the date, the name of the controller, a general comment, …

julian_ski · 2024-12-18T11:12:01.616Z

krenkel:

I’ll send you a printout in Excel, to see if this is what you want. That is to have a vehicle and keep the history of just one vehicle, but it’s in this idea, because I launch a car and then I’ll just launch its daily evaluations. And this will be for as many vehicles as you have. Is this the idea you want?

Like this :

Capture1279×611 11.8 KB

julian_ski · 2024-12-18T11:13:10.008Z

The test score can be a number or a text, I adapt

krenkel · 2024-12-18T11:26:52.585Z

@julian_ski, I’m almost reaching the conclusion that we’ll need to use a repeating group within another, called a nested repeating group. But I’m going to do a test, because if I have some element from table B that talks to table A, it might not be necessary, since all the data will come from a single table. But now I think we’re getting a direction. I’ll let you know. Thanks for now.

julian_ski · 2024-12-18T13:23:37.110Z

I tried on my side with backend workflows but nothing works. Either I set it wrong, or there is another problem.

krenkel · 2024-12-19T20:35:25.950Z

Hi @julian_ski, now that I’ve made some progress, I didn’t use lists as I thought I would need to, but I needed to adjust the tables well, I even created one more and re-did the fields. Below are prints, I save the data, and search in the car model field, and two types of filters appear, one with just one car name, and the other repeating the name, but the first filter is more complete and it will add and remove information. Below are two prints already filtered to generate the necessary reports per car. As you can see, the dates change and there are the names of the responsible parties.

filtro1971×713 89.3 KB

filtro2862×691 84.3 KB

julian_ski · 2024-12-20T14:06:22.412Z

Hello @krenkel, I don’t worry about the layout, I can organize it to make it work;

Can you record the different controls?

krenkel · 2024-12-22T14:46:35.993Z

Good morning @julian_ski ,
First of all, I apologize, I didn’t see your answer, here is the data.
Let’s go, I recreated the tables, we have 3 tables now: they are:
I also removed a repeat group to make it easier to understand.

tb_cad_veiculo
model type text

tb_responsavel
responsavel_vistoria type text

tb_verificacoes(or tb_vistoria)
data_verificação(and or Vistoria) type date
item checked type text
observações type text
responsável_id here is important this field here will communicate with the tb_responsavel table so it is of the tb_responsavel type, with that we have a relationship between tables.

Status(good, bad) type text
veiculo_id here again very important this field here will communicate with the tb_veiculo table so it is of the tb_veiculo type, with that we have a relationship between tables.
So this table is the most important one, where you will receive vehicle and responsible person registrations.

I also changed the concept of several dropdowns to just one, but that’s my way of seeing the situation. You can create it the way you think is best. The checked item dropdown will include cold weather, lights, etc., and you save one item and then save the other item. Everything I did here for testing purposes are just ideas for you. I’ll try to give you all the information.

In my test, I have a screen (layout) that isn’t good, but it’s functional. Here’s a printout of the main screen. There are three registration buttons, one for vehicles, another for responsible person, and the third is the inspection registration, which will include the other two registrations.

On this main screen, below the current date, we have the current date, which you can change. Next to it are the registrations, to be done before going to register the inspection (register inspection), which is where you can choose what you registered for the car and responsible person before.

Below are the repeater groups, one where there is an orange car icon, a popup will open with the selected car, this field does not need to be filled in as it will already save the selected car, then come the fields item verified responsible and status about the chosen car and click on change, and then it will appear in the first listing in order of date (of the orange car drawing icon)). To filter: you use the car model dropdown, and select a car that has some information released, a filter will be made on that respective car in the second repeatgroup, where the name of the selected car will appear and in the repeatgroup all the releases for that car will appear, this will serve as a report, later you can do by date and etc, it’s up to your imagination.

tela01748×681 70.5 KB

julian_ski · 2024-12-24T08:24:25.576Z

Hello krenkel

I understand the data structure.

Could you show me the workflow you used to record the information?
I have the impression that what you proposed is quite functional.
Indeed, the layout is not very important here.

Thank you and I wish you and your family a very Merry Christmas.

krenkel · 2024-12-24T12:22:25.071Z

Hi @julian_ski, here are the workflow screens( and yes, I’m terrible at layout ). I hope it gives you some ideas and that you can complete your project. I would also like to thank you for the opportunity to work together. Merry Christmas to you and your family and a great New Year and may new projects come your way. Thanks and good luck with your project. Joyeux noël

cad_responsavel1799×640 86.4 KB

cad_veiculo912×364 30.2 KB

cad_verificacoes(vistoria)936×542 45 KB

popup_dados_selecionados892×406 28.8 KB

system · 2025-02-16T22:37:07.418Z

This topic was automatically closed after 70 days. New replies are no longer allowed.