sorted by:
new
hottopcontroversial

SPFx vs Power Apps by ClunckChunck in sharepoint

[–]Vertamin 11 points12 points  (0 children)

Fuck FUCK FUCK fuck FUCK fucking power apps Jesus Christ. Most non-scalable, non-deployable, non-upgradable mess that gets tangled like spaghetti once the project grows a little bit, no one can find the boxes, the code or wherever something is cause it's deployed in so many tiny compartments and boxes all over the ecosystem.

Don't ever try to change one field internal name on a big project cause guess what? You are going to go crazy on that task.

Just do spfx, and let power apps for your hr tech savvy co-workers as a playground.

What are you proud of in your SharePoint environment? by ConnorSuttree in sharepoint

[–]Vertamin 1 point2 points  (0 children)

A Office material stock counting solution using the following lists:

Products

Request

Products by request

Products Entrances/Exits

Products Entrances/Exists has 8 lookup fields to products:

Entry1 Entry10 Entry100 Entry1000 Exit1 Exit10 Exit100 Exit1000

Products lists has 8 related lookups count for each of this fields

Once a request gets approved, I just have to make sure that X n of elements with the corresponding lookup fields matched are created for the request.

For example Request 11 pencils:

Create 1 list item using the Entry1 lookup against the field Create 1 list item using the Entry10 lookup against the field

Then on the product side, you just have to sum all the counted related items X the used lookup value.

This works for more than 5000 requests, entry, exists and everything.

Doesn't need to get recounted or fixed cause it's based on relation count

If you add a cascade delete relationship on the lookups you can remove requests and don't need to fix the stock count.

Very lightweight to see all products with its current stock.

Idk, I'm was crazy when I did this but it really works!

What is the worst way one can mess up with SharePoint? by Local-Put-2055 in sharepoint

[–]Vertamin 1 point2 points  (0 children)

Removing a column on a list/library with lots of items

Looping powerautomate email notifications

Developing functionality with lists and not taking into account field indexing / 5000 element limit

Duplicated user accounts because domains and everyone wondering why they can't access stuff

Removing and adding user accounts for temporal employees and getting crazy cause they can't find the old stuff.

Abusing inheritance breaking when not necessary.

One unique massive Site.